From: | "D'Arcy" "J(dot)M(dot)" Cain <darcy(at)druid(dot)net> |
---|---|
To: | rbrad(at)hpb50023(dot)boi(dot)hp(dot)com (Ryan Bradetich) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Sequences.... |
Date: | 1999-03-18 04:04:40 |
Message-ID: | m10NU2y-0000cIC@druid.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thus spake Ryan Bradetich
> > > > If we decide to leave things more or less as they are, how about a new
> > > > flag for sequences and indexes that sets a row as system generated
> > > > rather than user specified? We can then set that field when a sequence
> > > > or index is generated by the system such as for the serial type or
> > > > primary keys.
> > >
> > > Yes, it'd be nice to think about fixing up primary-key implicit indexes
> > > while we are at it --- they have some of the same problems as SERIAL ...
>
> I'm not following this... When a table is dropped, all the indexes for that
> table get dropped. The indexes are associated with a table, whereas the
> sequences are just sequences not associated with a table. Am I understanding
> the issue correctly?
I was thinking more for pg_dump. If it is a system index, don't dump it.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
From | Date | Subject | |
---|---|---|---|
Next Message | Wayne Piekarski | 1999-03-18 04:46:52 | Re: [HACKERS] vacuum slowness |
Previous Message | The Hermit Hacker | 1999-03-18 04:00:11 | Re: [HACKERS] One more globe |