[ADMIN] Extent size
Hello *, is there any way in postgres to define the size of extents ? regards -andreas -- Andreas Schmitz - Phone +49 201 8501 318 Cityweb-Technik-Service-Gesellschaft mbH Friedrichstr. 12 - Fax +49 201 8501 104 45128 Essen - email [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [ADMIN] Extent size
Andreas Schmitz wrote: Hello *, is there any way in postgres to define the size of extents ? We don't have extents like Informix. We use the file system so size is unlimited. I think that answers your question. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[ADMIN] pg_dump error
Hi, What does this mean ?!? Is this a corrupt database, a bug or has the pg_dump not enough memory ? And ... how can i solve this problem ? $ pg_dump login | gzip login.dump.gz pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293 pg_dump: lost synchronization with server, resetting connection pg_dump: SQL command to dump the contents of table postcodereeks failed: PQendcopy() failed. pg_dump: Error message from server: pg_dump: The command was: COPY postcodereeks TO stdout; $ psql -c 'COPY postcodereeks TO stdout;' login /tmp/postcodereeks ERROR: MemoryContextAlloc: invalid request size 4294967293 lost synchronization with server, resetting connection Config: Machine; dual PIII with 1 Gb memory DB version: PG 7.2.1 postgres.conf: zip shared_buffers = 2048 sort_mem = 1024 zip Regards, Ferdinand ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [ADMIN] Extent size
On Tuesday 01 October 2002 17:18, Bruce Momjian wrote: Andreas Schmitz wrote: Hello *, is there any way in postgres to define the size of extents ? We don't have extents like Informix. We use the file system so size is unlimited. I think that answers your question. Not really. If I want to store data in a efficient way I normally have a look at the size of the data. lets say I've got text blocks of 1.5 kb. I would consider to choose an extent size of 2kb instead of 4 kb to save up space. Which would be the right consideration for postgres ? regards -andreas -- Andreas Schmitz - Phone +49 201 8501 318 Cityweb-Technik-Service-Gesellschaft mbH Friedrichstr. 12 - Fax +49 201 8501 104 45128 Essen - email [EMAIL PROTECTED] ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [ADMIN] Extent size
Andreas Schmitz wrote: On Tuesday 01 October 2002 17:18, Bruce Momjian wrote: Andreas Schmitz wrote: Hello *, is there any way in postgres to define the size of extents ? We don't have extents like Informix. We use the file system so size is unlimited. I think that answers your question. Not really. If I want to store data in a efficient way I normally have a look at the size of the data. lets say I've got text blocks of 1.5 kb. I would consider to choose an extent size of 2kb instead of 4 kb to save up space. Which would be the right consideration for postgres ? We don't do such optimizations and consider them of limited value. Our pages are 8k, and we have backup tables for long values. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[ADMIN] Fwd: Fwd: FATAL 1: Database dialup does not exist in pg_database
This is a forwarded message From: roco [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Friday, September 27, 2002, 2:52:53 PM Subject: : FATAL 1: Database dialup does not exist in pg_database ===8==Original message text=== This is a forwarded message From: roco [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Friday, September 27, 2002, 2:49:47 PM Subject: FATAL 1: Database dialup does not exist in pg_database ===8==Original message text=== Hello, When I execute the command psql dialup , I receive this message: postgres@www:/usr/local/pgsql/data/base/dialup$ psql dialup Connection to database 'dialup' failed. FATAL 1: Database dialup does not exist in pg_database This data base was using. What can I do? -- Best regards, roco mailto:[EMAIL PROTECTED] ===8===End of original message text=== -- Best regards, rocomailto:[EMAIL PROTECTED] ===8===End of original message text=== -- Best regards, rocomailto:[EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [ADMIN] pg_dump error
Ferdinand Smit [EMAIL PROTECTED] writes: What does this mean ?!? Is this a corrupt database, a bug or has the pg_dump not enough memory ? $ pg_dump login | gzip login.dump.gz pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293 pg_dump: lost synchronization with server, resetting connection pg_dump: SQL command to dump the contents of table postcodereeks failed: PQendcopy() failed. First guess is a corrupted data value in table postcodereeks. Possibly you can narrow down which row(s) have bad data and remove 'em. regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [ADMIN] libreadline.so.3
Bai Yan writes: I have installed postgresql before (7.1.*, BTW, how can I check what version I am using after the installation - where can I get the version information?). postmaster --version psql --version Recently, the linux server is rebooted and upgraded. Since I am not the su, I have to rerun pgsql server. But when I tried as usual to restart the database server, I got error message this time as 'cannot open libreadline.so.3: no file exist'. there're several library files available as: libreadline.a libreadline.so.4librep.a librep.so.9 libresolv.a libreadline.so libreadline.so.4.2 what should I do to make pgsql recognize the library files in my system, while not just the one it expectes? Recompile PostgreSQL (after doing make distclean in your old tree). -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
