On Wed, Jan 21, 2004 at 04:54:26PM -0700, scott.marlowe wrote:
> On Wed, 21 Jan 2004, Kragen Sitaker wrote:
> > ... subject like 'Couldn%'" ... But I'm using Postgres 7.3.4, and
> > it doesn't seem to have varchar_pattern_ops in its pg_opclass.opcname. ..
I'd like to be able to do queries like "select count(*), fromline from
message where subject like 'Couldn%'" quickly. I see that, in current
Postgres, I can do this with an index like "create index message_subject
on message using btree(subject varchar_pattern_ops)". But I'm using
Postgres 7.3.4,
On Sat, Jan 10, 2004 at 11:20:11AM +1100, Martijn van Oosterhout wrote:
> Not really related to your problem, but given you're in a transaction, why
> do you need to lock anything? What's wrong with:
>
> > The daemon that gets this error does the following every 15 seconds:
> > - start a transacti
On Fri, Jan 09, 2004 at 06:19:00PM -0500, Tom Lane wrote:
> Kragen Sitaker <[EMAIL PROTECTED]> writes:
> > ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index
> > We've been getting this error in our application every once in a while
> &g
