From: Tom Lane <tgl@sss.pgh.pa.us>
To: justinb@tricord.com
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: Re: libpq++
Date: Thu, 03 May 2001 15:42:16 -0400
Message-ID: <818.988918936@sss.pgh.pa.us> (raw)
In-Reply-To: <15089.45940.490466.456420@idoru.tricord.com>
References: <200105031915.f43JFpf12056@candle.pha.pa.us>
<299.988917936@sss.pgh.pa.us>
<15089.45940.490466.456420@idoru.tricord.com>
Justin Banks <justinb@tricord.com> writes:
> You're right - this only works because the shared connections all
> occur in the same address space. It doesn't buy you anything between
> applications, only inside an application. The problem is that there's
> no way for different instantiations of classes inheriting
> database-ness from the PgDatabase class to share a PGconn* unless the
> PgDatabase class provides a way for different instantiations to know
> that existing connections are available.
And what's wrong with a static class variable for that purpose?
The shmem segment looks like the hardest possible way to get the
same result.
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@tricord.com, pgman@candle.pha.pa.us
Subject: Re: Re: libpq++
In-Reply-To: <818.988918936@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