Re: [HACKERS] Problems with >2GB tables on Linux 2.0 - Mailing list pgsql-hackers

From Tim Perdue
Subject Re: [HACKERS] Problems with >2GB tables on Linux 2.0
Date
Msg-id 009a01be7077$4e665120$0b8c5aa5@timnt.weather.net
Whole thread Raw
Responses Re: [HACKERS] Problems with >2GB tables on Linux 2.0
List pgsql-hackers
I am still not able to pg_dump my data after recovering from this disaster.
My files are now segmented at 1GB, vacuuming is fine, but pg_dump has a
problem "locating the template1 database".

I sure hope someone can help me come up with a way to safely backup this
data. Someone sent me a patch for the Linux Kernel that will allow it to
handle files > 2GB, but that won't help me with my backup problems.

Thanks,

Tim Perdue
geocrawler.com




-----Original Message-----
From: Tatsuo Ishii <t-ishii@sra.co.jp>
To: Peter Mount <petermount@it.maidstone.gov.uk>
Cc: t-ishii@sra.co.jp <t-ishii@sra.co.jp>; Tom Lane <tgl@sss.pgh.pa.us>;
pgsql-hackers@postgreSQL.org <pgsql-hackers@postgreSQL.org>
Date: Tuesday, March 16, 1999 10:45 PM
Subject: Re: [HACKERS] Problems with >2GB tables on Linux 2.0


>>Just a question. Does your patch let vacuum handle segmented tables?
>>--
>>Tatsuo Ishii
>
>>It simply reduces the size of each segment from 2Gb to 1Gb. The problem
>>was that some OS's (Linux in my case) don't like files exactly 2Gb in
>>size. I don't know how vacuum interacts with the storage manager, but in
>>theory it should be transparent.
>
>Ok. So we still have following problem:
>
>test=> vacuum smallcat;
>NOTICE:  Can't truncate multi-segments relation smallcat
>VACUUM
>
>Maybe this should be added to TODO if it's not already there.
>--
>Tatsuo Ishii



pgsql-hackers by date:

Previous
From: "D'Arcy" "J.M." Cain
Date:
Subject: Re: [HACKERS] Sequences....
Next
From: "D'Arcy" "J.M." Cain
Date:
Subject: Re: [HACKERS] Problems with >2GB tables on Linux 2.0