Re: SELECT Query returns empty

From: Klint Gore <kgore4(at)une(dot)edu(dot)au>
To: "Bright D(dot)L(dot)" <dl_bright(at)star-quest(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: SELECT Query returns empty
Date: 2008-07-10 05:33:49
Message-ID: 48759F3D.1010408@une.edu.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bright D.L. wrote:
> >Once step 6 completes, can psql see the data?
>
> Yes, P1 makes sure and is able to see the data before sending Packet to
> P2.
>

Not P1, but psql. If you can see the data from psql, then your problem
has to be in P2. If you can't see the data from psql, then P1 is the
problem.

> >Does "select * from pg_stat_activity" show anything unexpected?
>
> I have to investigate on that side.
>

If it's as everyone thinks, then one of them will probably be idle in
transaction when queried from psql between step 6 and 7. Running it
from P1 or P2 will just tell you that its running "select * from
pg_stat_activity", not if it's still in transaction.

You could try setting log_statement='all' and check that the logs look
like you would expect. Especially the commits from both sides.

klint.

--
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350

Ph: 02 6773 3789
Fax: 02 6773 3266
EMail: kgore4(at)une(dot)edu(dot)au

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Devrim GÜNDÜZ 2008-07-10 05:35:39 Re: Making a RPM installer
Previous Message Devrim GÜNDÜZ 2008-07-10 05:30:14 Re: Making a RPM installer