Re: Logs say update done but not actually done or committed into database ???

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Atul Chojar <achojar(at)airfacts(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Logs say update done but not actually done or committed into database ???
Date: 2009-04-22 20:47:08
Message-ID: 11573.1240433228@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Wed, Apr 22, 2009 at 2:28 PM, Atul Chojar <achojar(at)airfacts(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message DM 2009-04-22 22:19:27 how to revoke multiple users permission from multiple tables at the same time?
Previous Message Scott Marlowe 2009-04-22 20:30:37 Re: Logs say update done but not actually done or committed into database ???