Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [PATCHES] Implementing RESET CONNECTION ...
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
- Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>, eg(at)cybertec(dot)at
- Subject: Re: [PATCHES] Implementing RESET CONNECTION ...
- Date: Tue, 25 Apr 2006 11:27:07 -0400
- Message-id: <19532(dot)1145978827(at)sss(dot)pgh(dot)pa(dot)us>
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes: > Should we add it for 8.2 and see if we get any problem reports? No. I don't believe this can work without a far more invasive patch than this is. To point out just one problem, what of cached plans in plpgsql functions? Those can't be carried across a genuine connection reset (permissions and search path are two reasons why not). And the protocol issues are not something you can just ignore, because the command does break reasonable driver-level expectations. regards, tom lane
- References:
- Re: [PATCHES] Implementing RESET CONNECTION ...
- From: Bruce Momjian
- Re: [PATCHES] Implementing RESET CONNECTION ...
- Prev by Date: Re: TODO Item: ACL_CONNECT
- Next by Date: Re: [GENERAL] Concurrency problem building indexes
- Previous by thread: Re: [PATCHES] Implementing RESET CONNECTION ...
- Next by thread: FOR UPDATE lock problem ?
- Indexes: