Search Postgresql Archives

Re: pg_dump SERIAL and SEQUENCE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Oct 18, 2007, at 1:02 PM, Andreas Kretschmer wrote:

Laurent ROCHE <laurent_roche@xxxxxxxxx> schrieb:
Then when I drop tab_b, the SEQUENCE tab_b_colb1_seq is not dropped, however
when I drop tab_a,  the SEQUENCE tab_a_cola1_seq is dropped too !
I am using PG 8.1 and ALTER SEQUENCE ... OWNED BY does not exist ! ! !

Read this message: <28684.1192378480@xxxxxxxxxxxxx>

,----[  quote Tom Lane  ]
| In 8.2 and up you can use ALTER SEQUENCE ... OWNED BY ... to establish
`----

You see the difference?


Regards, Andreas

Andreas's point is that the OWNED BY clause was added in 8.2 to fix your issue and it is policy to not change functionality of older releases unless it is to fix an actual, proven error. Basically, if your sequence isn't owned by any particular table then it is considered an independent relation and you need to manage it's being dump/restored on its own just like with any other independent relation.

Erik Jones

Software Developer | Emma®
erik@xxxxxxxxxx
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
      choose an index scan if your joining column's datatypes do not
      match


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux