Hi all,
I am using Postgresql 8.2.
I am using client side api to upload/download files to/from postgresql using
calls lo_export()/lo_import();
If I download a file from postgresql, few weeks later, files object's
contents got damaged.
I don't know why.
Do any of you have encountered same probl
On Mon, May 08, 2006 at 12:09:13PM +0200, Francesco Dalla Ca' wrote:
> The PostgreSQL manual explain that from 8.1 the default behavior
> (governed by default_with_oids system parameter) is to create user
> tables "without oids".
>
> Well, at the page
> http://www.postgresql.org/docs/8.1/intera
The PostgreSQL manual explain that from 8.1 the default behavior
(governed by default_with_oids system parameter) is to create user
tables "without oids".
Well, at the page
http://www.postgresql.org/docs/8.1/interactive/datatype-oid.html , the
manual report this:
"Object identifiers (OIDs) ar
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> You should also change your application... IIRC the intention
> is to eventually remove OIDs from user tables.
There is no such plan --- defaulting to WITHOUT OIDS is as far as we
intend to go.
regards, tom lane
---
On Fri, Jan 13, 2006 at 11:05:38AM +0100, Szabolcs BALLA wrote:
> Hi,
>
> I have already upgraded our server from 7.4 to 8.1.
> My problem is the next: some of our queries use OIDS but I restored the
> databases without OIDS.
> Is it possible to set the OIDS without dump and restore?
No; the
Hi,
I have already upgraded our server from 7.4 to 8.1.
My problem is the next: some of our queries use OIDS but I restored the databases without OIDS.
Is it possible to set the OIDS without dump and restore?
Thanks
Szabek
Mark writes:
> Is there other meanings of oids than unique row identifier?
In normal user tables, OIDs don't mean anything unless you interpret
something into them. Nowadays, the advice is usually not to use OIDs, but
instead use user-defined sequences.
> Can I make two identical tables in the
Hello, All!
Is there other meanings of oids than unique row identifier?
Can I make two identical tables in the same database (even with oids)?
Something like this
CREATE TABLE table2 AS (SELECT oid,* FROM table1);
Or oids must be unique in whole database?
Mark
-
On Tue, May 27, 2003 at 10:01:03 -0400,
Jodi Kanter <[EMAIL PROTECTED]> wrote:
> I believe that I read something about OIDs being reintroduced in version
> 7.3.2. Can someone tell me why? Does this mean that the "without OIDs"
> feature is not an option in the newer version?
At most the defaul
Mathieu Arnold <[EMAIL PROTECTED]> writes:
> ... there's a bit more info in the 7.2 database now...
> so I believe that without oids give you a bit smaller databases.
OIDs vs. no OIDs makes absolutely *zero* difference in disk space.
The tuple header overhead is the same either way.
(Well, okay,
--On lundi 11 mars 2002 08:10 -0800 Heni Lolov <[EMAIL PROTECTED]> wrote:
> As for version 7.2 postgres supports tables wothout OID. So I have 10 Gb
> database and I would like to upgrade it to 7.2 to make the tables without
> oids in order to save disc space. I made a test. I created one table
Heni Lolov writes:
> As for version 7.2 postgres supports tables wothout OID. So I have 10 Gb
> database and I would like to upgrade it to 7.2 to make the tables without oids
> in order to save disc space. I made a test. I created one table with oids and
> another without oids and dumped the sam
Heni Lolov wrote:
> Hi
>
> As for version 7.2 postgres supports tables wothout OID. So I have 10 Gb
> database and I would like to upgrade it to 7.2 to make the tables without oids
> in order to save disc space. I made a test. I created one table with oids and
> another without oids and dumped
Hi
As for version 7.2 postgres supports tables wothout OID. So I have 10 Gb
database and I would like to upgrade it to 7.2 to make the tables without oids
in order to save disc space. I made a test. I created one table with oids and
another without oids and dumped the same data in both of them
14 matches
Mail list logo
