From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: Linux.conf.au 2003 Report |
Date: | 2003-01-30 02:57:51 |
Message-ID: | 1043895471.1210.51.camel@tokyo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On Wed, 2003-01-29 at 21:49, Christopher Kings-Lynne wrote:
> * IPV6 data types
Looks like this will be in 7.4, in one form or another.
> - The standard table modification tactic (that I also use) or renaming table
> to *_old and creating new one breaks because the primary key of the new
> table is assigned the same name as the PK of the old, causing CREATE TABLE
> to fail. This is really annoying. I think that auto-generated names should
> never collide.
Can this be accomplished without making auto-generated names ugly? And
if not, is it worth the trade-off?
> - I suggested that if pg_dump could dump individual schemas, then they could
> move their 'don't backup' tables to another schema, and just dump the other
> one.
FYI, I submitted a patch for this a couple weeks ago (although it hasn't
been applied yet...) -- it should be in 7.4
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2003-01-30 03:52:46 | Re: Linux.conf.au 2003 Report |
Previous Message | Christopher Kings-Lynne | 2003-01-30 02:49:25 | Linux.conf.au 2003 Report |
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2003-01-30 03:07:05 | Re: v7.2.4 bundled ... |
Previous Message | Christopher Kings-Lynne | 2003-01-30 02:49:25 | Linux.conf.au 2003 Report |