pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feeddata doesnt get saved in the database / idle in transaction
3+ messages / 3 participants
[nested] [flat]
* data doesnt get saved in the database / idle in transaction
@ 2006-03-20 10:46 Ksenia Marasanova <ksenia.marasanova@gmail.com>
2006-03-20 12:03 ` Re: data doesnt get saved in the database / idle in transaction Qingqing Zhou <zhouqq@cs.toronto.edu>
0 siblings, 1 reply; 3+ messages in thread
From: Ksenia Marasanova @ 2006-03-20 10:46 UTC (permalink / raw)
To: pgsql-performance
Hi,
I have a strange problem with my Postgres application. The problem is
that the data entered in the application never reaches the database,
although the record id (serial) is generated, and the record can be
retrieved again, and be modified. Multiple records can be added and
modified. But when i check the data with psql, the record is not
there.
The application uses persistant database connection, and when i check
the status of the connection, it shows: "idle in transaction". I am
pretty sure that every insert is being committed with explicit
"commit()" . It always worked before.... weird.
thanks for any hints
Ksenia.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: data doesnt get saved in the database / idle in transaction
2006-03-20 10:46 data doesnt get saved in the database / idle in transaction Ksenia Marasanova <ksenia.marasanova@gmail.com>
@ 2006-03-20 12:03 ` Qingqing Zhou <zhouqq@cs.toronto.edu>
2006-03-21 10:05 ` Re: data doesnt get saved in the database / idle in transaction Jim C. Nasby <jnasby@pervasive.com>
0 siblings, 1 reply; 3+ messages in thread
From: Qingqing Zhou @ 2006-03-20 12:03 UTC (permalink / raw)
To: pgsql-performance
""Ksenia Marasanova"" <ksenia.marasanova@gmail.com> wrote
>
> The application uses persistant database connection, and when i check
> the status of the connection, it shows: "idle in transaction". I am
> pretty sure that every insert is being committed with explicit
> "commit()" . It always worked before.... weird.
>
Try to use the following command to see what commands reach the server:
set log_statement = "all";
Regards,
Qingqing
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: data doesnt get saved in the database / idle in transaction
2006-03-20 10:46 data doesnt get saved in the database / idle in transaction Ksenia Marasanova <ksenia.marasanova@gmail.com>
2006-03-20 12:03 ` Re: data doesnt get saved in the database / idle in transaction Qingqing Zhou <zhouqq@cs.toronto.edu>
@ 2006-03-21 10:05 ` Jim C. Nasby <jnasby@pervasive.com>
0 siblings, 0 replies; 3+ messages in thread
From: Jim C. Nasby @ 2006-03-21 10:05 UTC (permalink / raw)
To: Qingqing Zhou <zhouqq@cs.toronto.edu>; +Cc: pgsql-performance
On Mon, Mar 20, 2006 at 08:03:14PM +0800, Qingqing Zhou wrote:
>
> ""Ksenia Marasanova"" <ksenia.marasanova@gmail.com> wrote
> >
> > The application uses persistant database connection, and when i check
> > the status of the connection, it shows: "idle in transaction". I am
> > pretty sure that every insert is being committed with explicit
> > "commit()" . It always worked before.... weird.
> >
>
> Try to use the following command to see what commands reach the server:
>
> set log_statement = "all";
I'd bet that the commits aren't making it over.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2006-03-21 10:05 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-03-20 10:46 data doesnt get saved in the database / idle in transaction Ksenia Marasanova <ksenia.marasanova@gmail.com>
2006-03-20 12:03 ` Qingqing Zhou <zhouqq@cs.toronto.edu>
2006-03-21 10:05 ` Jim C. Nasby <jnasby@pervasive.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox