Re: basic debugging question

From: Scott Frankel <leknarf(at)pacbell(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: basic debugging question
Date: 2004-10-26 21:33:18
Message-ID: A6E0CF5E-2796-11D9-9A77-000A95A7B782@pacbell.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


I should have *myself* committed.

Thanks for the suggestions (and OID tip)! It turned out that my script
was
not committing the transaction, so the insert was getting rolled-back.

Thanks
Scott

On Oct 26, 2004, at 12:39 PM, Scott Frankel wrote:

>
> I'm attempting to debug a script that should perform a simple INSERT
> of values,
> but for some reason doesn't. The insert appears to occur without
> error, printing
> "INSERT 18015 1 upon completion." Nonetheless, no data values appear
> to be
> added to the table when queried in psql.
>
> Questions:
>
> - What does the status msg, "INSERT 18015 1," refer to?
>
> - What is this output called? (So I can search the documentation for
> it.)
>
> - Is there something clever I can access -- besides this list ;) -- so
> I can
> peek inside INSERT 18015 1 to see what pgres is thinking about?
>
> Note that when I perform the INSERT by hand in psql, the row of data
> is entered
> without incident.
>
> Thanks in advance!
> Scott
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-10-26 21:59:27 Re: what could cause inserts getting queued up and db locking??
Previous Message Mike Mascari 2004-10-26 21:26:24 Re: primary key and existing unique fields