| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | justinb(at)mr-boo(dot)com |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, justinb(at)tricord(dot)com, PostgreSQL-interfaces <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: Re: libpq++ |
| Date: | 2001-05-03 19:13:00 |
| Message-ID: | 29887.988917180@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Justin Banks <justinb(at)mr-boo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-05-03 19:15:51 | Re: Re: libpq++ |
| Previous Message | Justin Banks | 2001-05-03 14:41:30 | Re: Re: libpq++ |