[BUGS] BUG #6572: The example of SPI_execute is bogus

2012-04-03 Thread umi . tanuki
The following bug has been logged on the website: Bug reference: 6572 Logged by: Hitoshi Harada Email address: umi.tan...@gmail.com PostgreSQL version: 9.1.3 Operating system: Any Description: http://www.postgresql.org/docs/9.1/static/spi-spi-execute.html === SPI_exe

Re: [BUGS] BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases

2012-04-03 Thread John R Pierce
On 04/03/12 9:40 AM, Tom Lane wrote: Alex Matzinger writes: > The connection that is executing the SELECT 1 are generally open for 1-5 > hours before they are killed. The specific connection only executes > SELECT 1. The transaction is simply BEGIN, and then SELECT 1's, no > other query i

Re: [BUGS] BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases

2012-04-03 Thread Kevin Grittner
Alex Matzinger wrote: > The connection that is executing the SELECT 1 are generally open > for 1-5 hours before they are killed. The specific connection > only executes SELECT 1. The transaction is simply BEGIN, and then > SELECT 1's, no other query is executed. Don't do that. In particula

Re: [BUGS] BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases

2012-04-03 Thread Tom Lane
Alex Matzinger writes: > The connection that is executing the SELECT 1 are generally open for 1-5 > hours before they are killed. The specific connection only executes > SELECT 1. The transaction is simply BEGIN, and then SELECT 1's, no > other query is executed. Lose the "BEGIN" and it will

Re: [BUGS] BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases

2012-04-03 Thread Alex Matzinger
The connection that is executing the SELECT 1 are generally open for 1-5 hours before they are killed. The specific connection only executes SELECT 1. The transaction is simply BEGIN, and then SELECT 1's, no other query is executed. The updates we make to the primary database are quiet large