From: | gabrielle <gorthx(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Mark Wong <markwkm(at)gmail(dot)com>, David Christensen <david(at)endpoint(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Explicit psqlrc |
Date: | 2010-06-23 13:17:51 |
Message-ID: | AANLkTimNs0y8DftqrRs6_BCbdomruKqumhOf67R--wRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 21, 2010 at 6:16 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Well, that might be a good idea, too, but my expectation is that:
>
> psql -f one -f two -f three
>
> ought to behave in a manner fairly similar to:
>
> cat one two three > all
> psql -f all
>
> and it sounds like with this patch that's far from being the case.
Correct. Each is handled individually.
Should I continue to check on ON_ERROR_ROLLBACK results, or bounce
this back to the author?
gabrielle
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-06-23 13:22:17 | Re: Explicit psqlrc |
Previous Message | Robert Haas | 2010-06-23 12:19:40 | Re: Cannot cancel the change of a tablespace |