Dropping the BEGIN has cleared up the issue. Thank you.
On 4/3/2012 9:50 AM, John R Pierce wrote:
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
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
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
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
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
On 03.04.2012 02:23, amatzin...@experts-exchange.com wrote:
On a hot standby database, while the primary is being updated, Postgres will
randomly kill a process which is performing a "Select 1" command.
The error is this:
2012-04-02 13:36:13.269
PDT,"smxuser","smxprd1",39523,"127.0.0.1:57893",4f
The following bug has been logged on the website:
Bug reference: 6571
Logged by: Alex Matzinger
Email address: amatzin...@experts-exchange.com
PostgreSQL version: 9.1.2
Operating system: Freebsd 7.4
Description:
On a hot standby database, while the primary is being up
