Re: Logs say update done but not actually done or committed into database ??? - Mailing list pgsql-admin

From Tom Lane
Subject Re: Logs say update done but not actually done or committed into database ???
Date
Msg-id 11573.1240433228@sss.pgh.pa.us
Whole thread Raw
In response to Re: Logs say update done but not actually done or committed into database ???  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-admin
Scott Marlowe <scott.marlowe@gmail.com> writes:
> On Wed, Apr 22, 2009 at 2:28 PM, Atul Chojar <achojar@airfacts.com> wrote:
>> Any ideas why above update is not working?

> Any possibility you're doing the updates to an inherited table, or a
> table in a different schema or a different database than you think?

Another possibility is that the script is issuing BEGIN and then not
sending a COMMIT before it exits.  In that case the behavior is going
to be auto-rollback, not auto-commit.  The psql invocation as given
doesn't show any sign of that, but maybe there's a \set AUTOCOMMIT off
hiding in ~/.psqlrc, or something like that?

            regards, tom lane

pgsql-admin by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Logs say update done but not actually done or committed into database ???
Next
From: DM
Date:
Subject: how to revoke multiple users permission from multiple tables at the same time?