Re: Feature freeze date for 8.1
От | Jim C. Nasby |
---|---|
Тема | Re: Feature freeze date for 8.1 |
Дата | |
Msg-id | 20050502210556.GZ47820@decibel.org обсуждение исходный текст |
Ответ на | Re: Feature freeze date for 8.1 (<adnandursun@asrinbilisim.com.tr>) |
Ответы |
Re: Feature freeze date for 8.1
|
Список | pgsql-hackers |
FWIW, I've found myself wishing I could set statement_timeout on a per user or per group basis. Likewise for log_min_duration_statement. On Mon, May 02, 2005 at 11:38:12PM +0300, adnandursun@asrinbilisim.com.tr wrote: > On Mon, 02 May 2005 19:53:56 -0000 > Andrew - Supernews <andrew+nonews@supernews.com> wrote: > > >The server-based method is actually no more complex to > >implement on the server end and does not impose any such > restrictions on > >the client (even if the client sets the option and then > ignores the database connection > >for a long time, all that happens is that the TCP window > fills up). > > Yes, any solution on the client side also requires all > client connection interface to be changed..But, at server > side solution only server side would be changed :-) I dont > know it is complex or not. as you know Oracle has a > parameter to implement that solution on the server side. > > Best Regards, > > Adnan DURSUN > ASRIN Bili?im Hiz.Ltd. > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match > -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"
В списке pgsql-hackers по дате отправления: