Bruce Badger wrote:
> > What I'd do, if I wanted to lock out old clients from accessing
> > particular tables, is just rename the tables to something else.
> > (Or keep using the same names, but put the tables in a schema or
> > database that old clients won't look in.) The clients wouldn't fail
> > very gracefully, perhaps, but the protocol-level hack doesn't qualify
> > as graceful in my book either ...
>
> I don't think that there is a graceful way to fix this. Unless I can
> pull off the "blocking old protocol versions" trick, it seems that the
> most likely option will come from another chance coincidence, i.e. that
> the StORE schema changes.
It would be nice if we could configure a function to run on connection
start. We have the ability to SET values per db or user, but not to
execute a function. The function could test SELECT version() and send a
message to the user.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073
