From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dietmar May" <dcmay(at)dmis(dot)com> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Race condition with libpq |
Date: | 2003-05-26 17:05:19 |
Message-ID: | 2388.1053968719@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
"Dietmar May" <dcmay(at)dmis(dot)com> writes:
> So, why can't the server-side code that closes the connection release any
> resources associated with that connection before the socket is closed? It
> seems that doing so could fix this problem quite cleanly.
How would that help? The client isn't waiting around for it, because it
already closed its socket.
> Perhaps I'm misunderstanding the manual - "4.1: When a new database is
> created, the template database [template1] is essentially cloned.
At least in recent versions, template1 is only the default template,
not the sole possibility.
In theory you could in fact run without any template1, but it would
break enough client-side code that I doubt anyone would find it useful
to do so in practice.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-05-26 17:06:36 | Re: [HACKERS] ECPG thread-safety |
Previous Message | Bruce Momjian | 2003-05-26 17:01:49 | Re: [HACKERS] ECPG thread-safety |