[Bucardo-general] CTL Creating Too Many syncrun Rows

Greg Sabino Mullane greg at endpoint.com
Sun Jul 28 02:20:33 UTC 2013

On Thu, Jul 25, 2013 at 06:40:32PM +0200, David E. Wheeler wrote:
> I’m tempted to add this:
>     CREATE UNIQUE INDEX syncrun_sync ON syncrun(sync) WHERE ended IS NULL;
> To both prevent bogus rows in the future, and to help figure out what is 
> happening should it happen again in the future.
> Should something like this go into the release schema?


> Ought we to consider adding other constraints to the database?

Probably. If for no other reason than to catch stuff like this quicker. The syncrun 
table is one of the few internal tables that can get quite large, but a single 
partial index like that should still be no problem.

Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Digital signature
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20130727/30d23dde/attachment.sig>

More information about the Bucardo-general mailing list