Hannu,
Thanks very much for showing me how to index log_xid on sl_log_1.

For everyone's info, I'd like to report that this does not seem to have
helped me with my inability to catch-up after a sync.  If there are
query changes within slony that could be tried, as discussed a week or
so ago, I would be pleased to be a guinea-pig for them.  The slony
version is 1.1.0, the postgres version 7.3.6

My provider database is very heavily loaded and it may be that it is
just working too damn hard for slony to keep up with.  I am going to
make another attempt to sync from scratch tonight without the extra
index.

In case I have done something stupid in my configuration, here it is:

# Do not log to syslog
syslog(0)

# Put a timestamp in log messages
log_timestamp(true)

# Lots of logging
log_level(2)

# Do fewer sync checks than is the default?
sync_interval(15000)

# Sync levery 15 seconds instead of 1 second?
sync_interval_timeout(15000)

# Maximum number of syncs that may be processed in one go.
sync_group_maxsize(1000)

#
desired_sync_time(0)

Thanks.
__
Marc


On Thu, 2005-09-15 at 23:59 +0300, Hannu Krosing wrote:
> On N, 2005-09-15 at 13:41 -0700, Marc Munro wrote:
> > Folks,
> > I saw a suggestion in this list about adding an index to sl_log(log_xid)
> > to speed up queries.  Can someone enlighten me on how to do this, I am
> > getting the following error:
> > 
> > ERROR:  data type _cage2.xxid has no default operator class for access
> > method "hash"
> > 	You must specify an operator class for the index or define a
> > 	default operator class for the data type
> > 
> > What do I need to specify for the opclass or access method or both?
> 
> look how it's done with the existing index (\d _xxe_cluster.sl_log_1)
> 
> original one:
> 
> "sl_log_1_idx1" btree (log_origin, log_xid _xxx_cluster.xxid_ops,
> log_actionseq)
> 
> what needs to be added:
>     "sl_log_1_idx2" btree (log_xid _xxx_cluster.xxid_ops)
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050916/7a7bb6c8/attachment.bin