> > If my memory serves me well, Oracle has a number of system triggers. On
> > database startup and shutdown and perhaps also on connection start and
> > stop.
> >
> > Sometimes they're very handy.
>
> Is this a TODO? Is there an API that would make sense for us?
I believe it would make sense. B
Kaare Rasmussen wrote:
> > 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
>
> If my memory serves me well, Oracle has a number of system triggers. On
> database startup and shutdown and perhaps also o
> 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
If my memory serves me well, Oracle has a number of system triggers. On
database startup and shutdown and perhaps also on connection start and stop.
Som
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
>
Robert Treat <[EMAIL PROTECTED]> writes:
> Tom, just curious as to what your resistance is to this feature? ISTM
> that making this admin modifiable doesn't hurt anyone and could be
> helpful to some people.
Admin modifiable at what level? I don't believe that the "feature" is
valuable enough to
On Fri, 2003-08-29 at 12:09, Tom Lane wrote:
> Bruce Badger <[EMAIL PROTECTED]> writes:
> > Unfortunately, I am not in a position to initiate a change in the StORE
> > schema. StORE is also used with other RDBMSs, and the users of those
> > have no incentive to bless a change in the schema just to
On Friday 29 August 2003 15:37, Bruce Badger wrote:
> On Fri, 2003-08-29 at 23:35, Tom Lane wrote:
> > Rod Taylor <[EMAIL PROTECTED]> writes:
> > >> So, being able to stop connections trying to use old protocol versions
> > >> would be very helpful in this case.
> > >
> > > Wouldn't it be better to
Bruce Badger <[EMAIL PROTECTED]> writes:
> Unfortunately, I am not in a position to initiate a change in the StORE
> schema. StORE is also used with other RDBMSs, and the users of those
> have no incentive to bless a change in the schema just to help out the
> PostgreSQL users.
Hm, I must have mi
On Fri, 2003-08-29 at 23:23, Rod Taylor wrote:
> > So, being able to stop connections trying to use old protocol versions
> > would be very helpful in this case.
>
> Wouldn't it be better to have StORE run a select version() after
> connecting? Even better would be to call PQprotocolVersion() as
On Fri, 2003-08-29 at 23:35, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> >> So, being able to stop connections trying to use old protocol versions
> >> would be very helpful in this case.
>
> > Wouldn't it be better to have StORE run a select version() after
> > connecting?
>
> Wel
Rod Taylor <[EMAIL PROTECTED]> writes:
>> So, being able to stop connections trying to use old protocol versions
>> would be very helpful in this case.
> Wouldn't it be better to have StORE run a select version() after
> connecting?
Well, his point is that old versions of his client code wouldn't
> So, being able to stop connections trying to use old protocol versions
> would be very helpful in this case.
Wouldn't it be better to have StORE run a select version() after
connecting? Even better would be to call PQprotocolVersion() as it is a
protocol issue.
signature.asc
Description: This
On Fri, 2003-08-29 at 13:23, Tom Lane wrote:
> Bruce Badger <[EMAIL PROTECTED]> writes:
> > Will it be possible to tell a PostgreSQL back end to use *only* the new
> > version of the FE/BE protocol?
> > That is, will it be possible to set up a database that will reject
> > connection attempts that
Bruce Badger <[EMAIL PROTECTED]> writes:
> Will it be possible to tell a PostgreSQL back end to use *only* the new
> version of the FE/BE protocol?
> That is, will it be possible to set up a database that will reject
> connection attempts that do not use the new protocol version?
I cannot imagine
Will it be possible to tell a PostgreSQL back end to use *only* the new
version of the FE/BE protocol?
That is, will it be possible to set up a database that will reject
connection attempts that do not use the new protocol version?
Thanks,
Bruce
signature.asc
Description: This is a di
Will it be possible to tell a PostgreSQL back end to use *only* the new
version of the FE/BE protocol?
That is, will it be possible to set up a database that will reject
connection attempts that do not use the new protocol version?
Thanks,
Bruce
---(end of bro
16 matches
Mail list logo
