Re: dbmirror modifies pg_proc nextval/setval functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "James Doherty" <JDoherty(at)yak(dot)ca>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: dbmirror modifies pg_proc nextval/setval functions
Date: 2005-06-01 17:19:15
Message-ID: 16945.1117646355@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"James Doherty" <JDoherty(at)yak(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2005-06-01 23:28:01 Re: [ADMIN] Config option log_statement
Previous Message James Doherty 2005-06-01 16:30:37 dbmirror modifies pg_proc nextval/setval functions