I wish to see the results of the queries, especially when there are errors.
But also to track (and control) who makes DDL changes and what they were
exactly.  slonik << | tee log.out was not giving me the query output.

This is easy even with many parallel databases using psql.  I get a canonical
successful run and diff the stdout from other runs to it to do a fast
and accurate test for success as well as tracking when doing ddl updates.
I wanted to do the same thing with parallel slony clusters.

When I found I could not get the same output from slony, I had to change
my technique and only log who and when.  I'd really like the output of
the script, too.

The more the output looks like the psql output of a script run the
better.  If that means running the individual queries, so be it.


--elein

On Wed, Mar 15, 2006 at 04:12:54PM -0500, Christopher Browne wrote:
> One of our QA guys was doing some testing on this, and was wondering
> what output should come from EXECUTE SCRIPT.
> 
> After thinking about it, a bit, two conclusions came out:
> 
> 1.  For 1.1.5, there isn't a valid answer for this.
> 
> In 1.1.5, EXECUTE SCRIPT handles the entire script as one query in one
> not-entirely-so-swell foop, so that there would only be a notion of
> getting one set of command results out of it, however many queries may
> have been involved.
> 
> 2.  For 1.2, we split the query set into individual queries, and run
> them one by one.
> 
> At that point, "what an idea!", why don't we:
> 
>  a) Output the statement to [stdout, for slonik|logs, for slon]
>  b) Output the command result to [stdout, for slonik|logs, for slon]
> 
> That strikes me as making it *way* less "magical" to users.
> 
> Comments?  Suggestions?  Bricks thru windows?
> -- 
> let name="cbbrowne" and tld="ca.afilias.info" in String.concat "@" [name;tld];;
> <http://dba2.int.libertyrms.com/>
> Christopher Browne
> (416) 673-4124 (land)
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general
>