Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] possible to create multivalued index from xpath() results in 8.3?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Matt Magoffin" <postgresql(dot)org(at)msqr(dot)us>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] possible to create multivalued index from xpath() results in 8.3?
Date: 2007-11-26 12:53:41
Message-ID: 200711261353.41889.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Am Freitag, 23. November 2007 schrieb Tom Lane:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Tom Lane wrote:
> >> Should we force initdb to correct these pg_proc entries, or just quietly
> >> change pg_proc.h?
> >
> > Considering the extent of the changes, I'd be in favor of forcing an
> > initdb.
>
> Well, if you're going to change the contents of pg_cast then there is
> little choice.  I was considering something less invasive ...

I will hang on to this patch for a few more days to see if any invasive 
catalog changes come out of the quote_literal/set_config discussion.  If not, 
I'll consider a less invasive solution.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

pgsql-hackers by date

Next:From: mac_man2005Date: 2007-11-26 13:24:40
Subject: Re: Replacement Selection
Previous:From: Heikki LinnakangasDate: 2007-11-26 12:35:42
Subject: Re: Replacement Selection

pgsql-general by date

Next:From: Jeff LarsenDate: 2007-11-26 13:25:04
Subject: Re: replication in Postgres
Previous:From: AndrusDate: 2007-11-26 11:29:50
Subject: Re: Why LIMIT and OFFSET are commutative

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group