From: | Daniel Stolk <stolkd(at)email(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | How to make a read-write atomic? |
Date: | 1999-09-02 01:00:46 |
Message-ID: | 37CDCC3E.AE36420@email.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I used to use the BEGIN-COMMIT pair in order to ensure that two
processes didn't read the same data and write at the same time, so
messing things up. But I've recently upgraded to the latest version of
postgresql and now it doesn't work anymore. Does anybody know what's
going on?
To explain my situation in more detail:
I want a process to read the database for the entry that has the highest
customerid number. I then want the process to write the next entry into
the database with a customerid that is one larger. But if two processes
read at the same time, then they will both write an entry that has the
same customerid number. How do I keep this from occurring since the
BEGIN command doesn't seem to work for me anymore?
I am using PostgreSQL 6.5.1 on RedHat 6.0
Thanks, Daniel Stolk
From | Date | Subject | |
---|---|---|---|
Next Message | omid omoomi | 1999-09-02 01:15:22 | Re: [GENERAL] How to make a read-write atomic? |
Previous Message | Robert Wagner | 1999-09-02 00:38:47 | Re: [GENERAL] How to make a read-write atomic? |