| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Chris Redekop <chris(at)replicon(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Database system identifier via SELECT? |
| Date: | 2011-12-08 21:11:19 |
| Message-ID: | 4EE127F7.8090908@commandprompt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/08/2011 12:57 PM, Bruce Momjian wrote:
>
> Chris Redekop wrote:
>> Is there any way to get the database system identifier via a select
>> statement? I have a primary/secondary async replication setup, and I'd
>> like be able to verify from the client side that the provided primary and
>> secondary connection strings do in fact refer to the same data set...
>
> Wow, that is a reasonable thing to want available via SQL, but I can't
> see a way to get to it.
>
> The only method I can suggest is to write a server-side C function that
> calls GetSystemIdentifier().
This seems like something we should have in core, don't you think?
JD
>
--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2011-12-08 21:15:58 | Re: Database system identifier via SELECT? |
| Previous Message | Bruce Momjian | 2011-12-08 20:57:24 | Re: Database system identifier via SELECT? |