Great, super thanks!
Sebastjan
On 10/29/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> I wrote:
> > "Sebastjan Trepca" <[EMAIL PROTECTED]> writes:
> >> This is how to reproduce this issue:
> >> ...
> >> inh_test=# alter table capitals inherit cities;
>
> > Fascinating. pg_dump is almost smart enough
I wrote:
> "Sebastjan Trepca" <[EMAIL PROTECTED]> writes:
>> This is how to reproduce this issue:
>> ...
>> inh_test=# alter table capitals inherit cities;
> Fascinating. pg_dump is almost smart enough to get this right, ...
I've fixed this --- if you need a patch right away, see here:
http://ar
"Sebastjan Trepca" <[EMAIL PROTECTED]> writes:
> This is how to reproduce this issue:
> ...
> inh_test=# alter table capitals inherit cities;
Fascinating. pg_dump is almost smart enough to get this right, except
that what it spits out is
ALTER TABLE capitals ALTER COLUMN id SET DEFAULT
nextval(
Hi,
sorry for late response and lack of details. Postgresql version is 8.2.5 .
This is how to reproduce this issue:
inh_test=# CREATE TABLE cities (
inh_test(# id serial,
inh_test(# nametext,
inh_test(# population float,
inh_test(# altitudeint -- in f
"Sebastjan Trepca" <[EMAIL PROTECTED]> writes:
> Current state:
> Table B has a primary key with sequence b_seq. Table A also has a
> primary key with sequence a_seq.
In view of the fact that primary keys aren't inherited, and do not
"have sequences", this description is uselessly imprecise. Ple
Hi,
I noticed a small bug/problem when restoring a database that uses inheritance.
Lets say you have a table B that inherits from table A.
Current state:
Table B has a primary key with sequence b_seq. Table A also has a
primary key with sequence a_seq.
Now we create a backup and restore the da
