Bug 188 - ERROR: more than one row returned by a subquery used as an expression
Summary: ERROR: more than one row returned by a subquery used as an expression
Status: RESOLVED FIXED
Alias: None
Product: Slony-I
Classification: Unclassified
Component: other scripts (show other bugs)
Version: devel
Hardware: All All
: medium major
Assignee: Christopher Browne
URL:
Depends on:
Blocks:
 
Reported: 2010-12-31 08:59 UTC by Christopher Browne
Modified: 2010-12-31 09:01 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Browne 2010-12-31 08:59:16 UTC 
Tests occasionally get hung up for a while when a slon process complains for a while with the following error:

Dec 31 11:47:25 cbbrowne postgres[13812]: [2-1] ERROR:  more than one row returned by a subquery used as an expression
Dec 31 11:47:25 cbbrowne postgres[13812]: [2-2] STATEMENT:  select count(*) from "_slony_regress1".sl_log_1 l
Dec 31 11:47:25 cbbrowne postgres[13812]: [2-3] #011where not(txid_visible_in_snapshot(l.log_txid, (select ev_snapshot from "_slony_regress1".sl_event where ev_timestamp = (select max(ev_timestamp) from "_slony_regress1".sl_event))));

The trouble here is that there may be multiple snapshots with the same timestamp.

Problem is in tests/poll_cluster.sh