Re: Schema version management

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Aidan Van Dyk <aidan(at)highrise(dot)ca>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joel Jacobson <joel(at)trustly(dot)com>, Vik Reykja <vikreykja(at)gmail(dot)com>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Schema version management
Date: 2012-07-07 19:46:11
Message-ID: 1341690236-sup-4978@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Excerpts from Aidan Van Dyk's message of sáb jul 07 11:32:33 -0400 2012:
>
> On Fri, Jul 6, 2012 at 4:50 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>
> > I have code in the wild that defines new operators and casts and has no
> > C code and is not in an extension and has no business being in an
> > extension.
>
> Nobody is claiming that pgdump shouldn't dump it.
>
> But, since you're using operators, what would you think is an
> appropriate name for the file the operator is dumped into?

I was thinking that it might make sense to group operators according to
the type(s) they operate on, somehow. Using funny chars for names is
guaranteed to cause problems somewhere.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-07-07 19:46:26 Re: regex_fixed_prefix() is still a few bricks shy of a load
Previous Message Jeff Janes 2012-07-07 19:35:33 Re: pg_prewarm