| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: BEGIN strange behaviour |
| Date: | 2007-11-22 13:28:25 |
| Message-ID: | 20071122132825.GN21682@crankycanuck.ca |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Nov 22, 2007 at 02:10:49PM +0100, luca(dot)ciciriello(at)email(dot)it wrote:
> I've sperimented a strange behaviour using the command BEGIN and COMMIT in a
> multi-threaded Linux environment.
> In one of the two thread I use I've got the following message after
> PQexec(myconn, "BEGIN;");
Uh, are your two threads using one connection? That's never safe.
> The same commands (inside the same code) runs fine in Windows and in MacOS
> X.
If you're using one connection and two threads, this is some accident of the
client, and nothing more.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francesco Esposito | 2007-11-22 13:35:14 | Re: BEGIN strange behaviour |
| Previous Message | Marco Bizzarri | 2007-11-22 13:28:08 | Re: backup of postgres scheduled with cron |