| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Patrick Hess <posi(at)pbone(dot)biz> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: OID problem |
| Date: | 2004-03-23 15:50:44 |
| Message-ID: | 20740.1080057044@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Patrick Hess <posi(at)pbone(dot)biz> writes:
> The only problem I have is related to this OID stuff -- I read a bit
> about this and found a way to solve my initial problems by creating my
> tables with "WITHOUT OIDS" -- works fine and CMS runs like on the
> original plattform (even faster but that's an other story).
> Now my real problem is that the CMS itself creates new tables for new
> asset types and does not create the tables using "WITHOUT OIDS".
Why do you care?
> Now my question: Is it possible somehow to switch for a complete
> database to WITHOUT OIDS so that tables are created without oid by
> default?
There is a switch for that in CVS tip, but not in existing releases IIRC.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guy Fraser | 2004-03-23 16:00:58 | Re: PHP or JSP? That is the question. |
| Previous Message | Cott Lang | 2004-03-23 15:49:15 | Re: PHP or JSP? That is the question. |