From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dietmar May <dcmay@dmis.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Race condition with libpq
Date: Mon, 26 May 2003 12:30:16 -0400
Message-ID: <2072.1053966616@sss.pgh.pa.us> (raw)
In-Reply-To: <008401c3239e$1cd6ccf0$fb02a8c0@muskrat>
References: <008401c3239e$1cd6ccf0$fb02a8c0@muskrat>
"Dietmar May" <dcmay@dmis.com> writes:
> Would I be right in guessing (from your comments) that if PQexec issues a
> command that does not return a result set, that it executes it
> asynchronously?
PQexec is synchronous. Connection closure is not, though: there is no
response from the backend (and hardly could be).
> That's the only way that I could see this could fail -- because my code
> can't issue a CREATE DATABASE until after the PQexec("DROP DATABASE") has
> returned.
You're missing the point. It's the DROP that's failing, not the CREATE,
and it's failing because the old backend is still connected to the
victim database.
> I guess I had misread the first statement as meaning "you can drop the
> template1 database and have a cluster that doesn't contain a database called
> template1"; but this is apparently not a valid interpretation, since PGsql
> seems to use template1 for many internal operations.
It is not used for any "internal" operations. It is conventionally
present so that clients have a standard place to connect to.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, dcmay@dmis.com
Subject: Re: Race condition with libpq
In-Reply-To: <2072.1053966616@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox