Jan Wieck <[EMAIL PROTECTED]> writes: >> that plpgsql's handling of command-counter changes is broken, but it >> does not follow that sprinkling the code with SetQuerySnapshot is wise. > Why do you blame PL/pgSQL for that? I don't see a single > reference to the command counter from the PL/pgSQL sources. > All it does is using SPI. So does "using SPI" by itself count > as "boken"? Sorry: SPI is broken, not plpgsql. Does that make you feel better? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
- RE: [HACKERS] PL/pgSQL bug? Tatsuo Ishii
- Re: [HACKERS] PL/pgSQL bug? Tom Lane
- Re: [HACKERS] PL/pgSQL bug? Tatsuo Ishii
- Re: [HACKERS] PL/pgSQL bug? Tom Lane
- RE: [HACKERS] PL/pgSQL bug? Hiroshi Inoue
- Re: [HACKERS] PL/pgSQL bug? Tom Lane
- [HACKERS] Re: PL/pgSQL bug? Hiroshi Inoue
- [HACKERS] Re: PL/pgSQL bug? Hiroshi Inoue
- [HACKERS] Re: PL/pgSQL bug? Hiroshi Inoue
- Re: [HACKERS] PL/pgSQL bug? Jan Wieck
- Re: [HACKERS] PL/pgSQL bug? Tom Lane
- Re: [HACKERS] PL/pgSQL bug? Jan Wieck
- Re: [HACKERS] PL/pgSQL bug? Hannu Krosing
- Re: [HACKERS] PL/pgSQL bug? Tom Lane
- Re: [HACKERS] PL/pgSQL bug? Hannu Krosing
- Re: [HACKERS] PL/pgSQL bug? Bruce Momjian
- Re: [HACKERS] PL/pgSQL bug? Bruce Momjian
- Re: [HACKERS] PL/pgSQL bug? Hiroshi Inoue
- [HACKERS] PL/pgSQL bug? Tatsuo Ishii
- Re: [HACKERS] PL/pgSQL bug? Tom Lane
- Re: [HACKERS] PL/pgSQL bug? Jan Wieck