... and the same for SELECT/INTO Also, the hasoids (or equivalent)
attribute is not picked up from the source table which would be another
way to push this property into the target table.
One or both of these mechanisms (I'd think both should be available)
would seem to be required to make these constructs useful in
environments requiring OIDs.
This seems to be a trivial but serious omission for this release.
Comments and suggestions?
- Thomas
From a syntax PoV, CREATE TABLE name WITH OIDS AS ... works. Haven't
worked out how to do the same for SELECT/INTO.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
- Re: [HACKERS] CREATE TABLE/AS does not allow WITH OIDS? Thomas Lockhart
- Re: [HACKERS] CREATE TABLE/AS does not allow WITH OID... Neil Conway
- Re: [HACKERS] CREATE TABLE/AS does not allow WITH... Thomas Lockhart
- Re: [HACKERS] CREATE TABLE/AS does not allow WITH... Tom Lane
- Re: [HACKERS] CREATE TABLE/AS does not allow ... Thomas Lockhart
- Re: [HACKERS] CREATE TABLE/AS does not al... Tom Lane
- Re: [HACKERS] CREATE TABLE/AS does n... Bruce Momjian