Michael, I didn't see the last comment in my previous replies. I know
that the variable isn't set because I embedded \set into the psql
commands so that they would output what is set.
Thanks,
Brad
Michael Fuhr wrote:
>On Fri, Jan 14, 2005 at 12:03:02PM +0000, Bradley Kieser wrote:
>
>
>
>>I have an admin script that drops a schema and then recreates it (quick
>>way to refresh from backup). However, if the schema doesn't exist, the
>>drop errors, as you would expect. The next SQL command, the schema
>>create, is never executed.
>>
>>
>
>How do you know the create is never executed? Are you looking for
>the schema and not finding it? How are you looking? Or is there
>an error message? What is it?
>
>Are you doing the drop and create in the same transaction? If so,
>then the drop statement's failure is preventing subsequent statements
>in that transaction from executing. If that's not the problem then
>please post a self-contained test case so we can see exactly what
>you're doing.
>
>
>
>>I do not have ON_ERROR_STOP set so why is this happening?
>>
>>
>
>How do you know ON_ERROR_STOP isn't set? Could it be set in
>a .psqlrc file? What does \set show?
>
>
>