From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Doherty <JDoherty@yak.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: dbmirror modifies pg_proc nextval/setval functions
Date: Wed, 01 Jun 2005 13:19:15 -0400
Message-ID: <16945.1117646355@sss.pgh.pa.us> (raw)
In-Reply-To: <6821EB3812B51A478DA36DE250D983288C01BE@fs7ottawa.yak.ca>
References: <6821EB3812B51A478DA36DE250D983288C01BE@fs7ottawa.yak.ca>
"James Doherty" <JDoherty@yak.ca> writes:
> This changing of the name of what I would think is a pretty basic
> function seems pretty risky.
My, that *is* ugly isn't it? Not to mention that the replacement setval
functions are created with the wrong argument datatypes. This looks
exceedingly broken to me.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, JDoherty@yak.ca
Subject: Re: dbmirror modifies pg_proc nextval/setval functions
In-Reply-To: <16945.1117646355@sss.pgh.pa.us>
References: <6821EB3812B51A478DA36DE250D983288C01BE@fs7ottawa.yak.ca> <16945.1117646355@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