>> 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 need
>hi,
>have a look at transaction isolation in docs
Thanks TM. I checked the isolation level of the DB and it is "read
committed". May be I will change it to 'Serializable' and check whether
that helps.
>/tm
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
>> The scenario:
>> There are two separate processes ? one (P1) inserting
(not
>> updating) data to a table at a high rate (around one record in 10ms)
and
>> another (P2) selecting the data from the same table for further
>>processing. P1
>> and P2 use separate connection to the Databas
Thank you Craig,
>At a guess: transactional visibility. P1 will have not yet committed
its
>transaction, so the data isn't visible to P2 yet. Remember, PostgreSQL
>defaults to the READ COMMITTED isolation level and does not offer READ
>UNCOMMITTED for those rare situations where you might want it.
Hi All,
I would really appreciate if any one can help me out on the
problem that I am facing with PostgreSQL.
The following is the system (Dell laptop) configuration:
Windows XP - SP2, Intel Core 2Duo, 2GB RAM
PostgreSQL v 8.3.3
The scenario:
There are t
