Problem with duplicate file.
Hi,
I work with a database PostgreSQL 7.3.1 on Linux.
I observe that the size of my database is bigger and when I verify the size for each file on the database directory, I remark that
one of this files (16404) is duplicate in two files : 16404.1 and 16404.2.
Moreover, the files 16404 and 16404.1 have the same size (1 Giga)
I don't understand why the file (16404) is duplicate in two another files 16404.1 and 16404.2.
I don't undertand this architecture. Could you give me an explication ?
Best regards,
Annie.
------------------------------------------
Faites un voeu et puis Voila ! www.voila.fr
I don't see anything in this that's a bug report, so I'm redirecting to
-general.
On Wed, 25 Jun 2003, [utf-8] abremond@voila.fr wrote:
I work with a database PostgreSQL 7.3.1 on Linux.
I observe that the size of my database is bigger and when I verify the
size for each file on the database directory, I remark that one of
this files (16404) is duplicate in two files : 16404.1 and 16404.2.
Moreover, the files 16404 and 16404.1 have the same size (1 Giga)
I don't understand why the file (16404) is duplicate in two another
files 16404.1 and 16404.2.
I don't undertand this architecture. Could you give me an explication ?
IIRC, some systems have trouble with large files, PostgreSQL breaks the
data for tables at one gigabyte boundaries. So 16404 is the first gig,
16404.1 is the second, etc...
On Fri, Jun 27, 2003 at 03:43:14PM -0700, Stephan Szabo wrote:
I don't see anything in this that's a bug report, so I'm redirecting to
-general.On Wed, 25 Jun 2003, [utf-8] abremond@voila.fr wrote:
I work with a database PostgreSQL 7.3.1 on Linux.
I observe that the size of my database is bigger and when I verify the
size for each file on the database directory, I remark that one of
this files (16404) is duplicate in two files : 16404.1 and 16404.2.
Moreover, the files 16404 and 16404.1 have the same size (1 Giga)
I don't understand why the file (16404) is duplicate in two another
files 16404.1 and 16404.2.
I don't undertand this architecture. Could you give me an explication ?IIRC, some systems have trouble with large files, PostgreSQL breaks the
data for tables at one gigabyte boundaries. So 16404 is the first gig,
16404.1 is the second, etc...
Correct, It just means the table exceeded 2GB.
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
Show quoted text
"the West won the world not by the superiority of its ideas or values or
religion but rather by its superiority in applying organized violence.
Westerners often forget this fact, non-Westerners never do."
- Samuel P. Huntington
[In future, please respond to the list]
On Mon, Jun 30, 2003 at 04:09:42PM +0200, abremond@voila.fr wrote:
Following your last mail, I remark that the table pg_largeobject is very large (3 files 16404 + 16404.1 + 16404.2).
I don't understand because, I have deleted many rows with larges Objects (OID), but my database doesn't decrease.
And when I apply a vacuumdb full the size of my database doesn't change.
How I can manage the table pg_largeobject ?
Because I think that there are many data in the table pg_largeobject, which are not refrenced in my database.
Thank you for your help.
I have no experience of large-objects. It is possible that you are not
deleting them properly when you delete the references from other tables.
Hopefully someone else on this list can help you.
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
Show quoted text
"the West won the world not by the superiority of its ideas or values or
religion but rather by its superiority in applying organized violence.
Westerners often forget this fact, non-Westerners never do."
- Samuel P. Huntington
Import Notes
Reply to msg id not found: HHASO6$57DF794F92777A0F9832CDF6ACAF30F7@voila.frReference msg id not found: HHASO6$57DF794F92777A0F9832CDF6ACAF30F7@voila.fr | Resolved by subject fallback