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: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org
Subject: Re: SELECT Query returns empty
Date: 2008-07-10 02:41:15
Message-ID: 487576CB.3070805@une.edu.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bright D.L. wrote:
> Processes P1 and P2 are executables developed in VC++. These are the
> steps performed by P1 before sending the TCP packet (which acts as a
> trigger) to P2.
>
> 1) Create an insertion query
> 2) Execute the query
> 3) Execute a 'Commit' command
> 4) Repeat 2 and 3 how many ever times needed
> 5) 'Select' part of the last 'insert'ed data to verify whether it is
> accessible
> 6) Repeat 6 till the data is available
> 7) Send a TCP packet to P2 to start its 'Select' query
>

Is there any chance that P2 is still in transaction from its last query?

Once step 6 completes, can psql see the data?

Does "select * from pg_stat_activity" show anything unexpected?

Are you directly using libpq or some other connection method?

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Hendra 2008-07-10 02:53:43 Array as parameter for stored procedure
Previous Message Bright D.L. 2008-07-10 02:32:14 Re: SELECT Query returns empty