From: Tom Lane <tgl@sss.pgh.pa.us>
To: justinb@mr-boo.com
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: justinb@tricord.com, PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: Re: libpq++
Date: Thu, 03 May 2001 15:13:00 -0400
Message-ID: <29887.988917180@sss.pgh.pa.us> (raw)
In-Reply-To: <15085.24280.868910.556829@dervish.mr-boo.com>
References: <15084.18414.123450.642118@idoru.tricord.com>
<200104292004.f3TK4nf21949@candle.pha.pa.us>
<15085.24280.868910.556829@dervish.mr-boo.com>
Justin Banks <justinb@mr-boo.com> writes:
> As one would have expected, I've found a problem. The c++ std. says that
> Automatic objects are not destroyed as a result of calling exit(), and so, a
> automatic PgDatabase in main() (or most anywhere, actually), would not have
> it's destructor called during an exit(), thereby leaving junk shm. segments
> around.
Unless your kernel is broken, application exit will cause the backend
connection to be closed, whereupon the backend will exit gracefully.
I see nothing to worry about here.
I'm not sure where you got this notion that clients get to touch any
of Postgres' shared memory ;-) but they don't.
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, justinb@mr-boo.com, pgman@candle.pha.pa.us
Subject: Re: Re: libpq++
In-Reply-To: <29887.988917180@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