Re: pgsql8.1: About COPY Command and system clomn oid - Mailing list pgsql-bugs

From Qingqing Zhou
Subject Re: pgsql8.1: About COPY Command and system clomn oid
Date
Msg-id dnf99u$1per$1@news.hub.org
Whole thread Raw
In response to pgsql8.1: About COPY Command and system clomn oid  (wangshj <wangshj@sduept.com>)
List pgsql-bugs
"wangshj" <wangshj@sduept.com> wrote
>
> oidtest=# COPY oidtest (name) WITH OIDS FROM stdin;
> Enter data to be copied followed by a newline.
> End with a backslash and a period on a line by itself.
>>> 54513        copyname
>>> \.
> oidtest=# INSERT INTO oidtest ( name ) VALUES( 'name2' ) ;
> INSERT 54513 1
> oidtest=# SELECT oid,name from oidtest ;
>  oid  |   name
> -------+----------
> 54512 | name1
> 54513 | copyname
> 54513 | name2
> (3 rows)
>
> oidtest=#
> Then I got two records with same oid(54513).
>

This is not a bug. You can specify any valid number here as Oids. If you
don't want duplicated Oids or strange Oids, then don't specify WITH OIDS
clause.

Regards,
Qingqing

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2106: EXPLAIN ANALYZE with SELECT query causes a single backend server process to segfault
Next
From: Tom Lane
Date:
Subject: Re: BUG #2106: EXPLAIN ANALYZE with SELECT query causes a single backend server process to segfault