Hi,
I have a beefy server with 2 SANs, 1 "fast" (A) and 1 "slow" (B) and 1.3TB worth
of 8.4.4 databases on A. A needs to be replaced/wiped completely with as little
downtime as possible. It's flash-based and the modules need to be replaced, so
no "swapping the SAN and keeping the disks". The d
Am 09.06.2010 16:37, schrieb Tom Lane:
Marinos Yannikos writes:
It seems that poll() never receives a connection closed notification under Linux
(https://lists.linux-foundation.org/pipermail/bugme-new/2003-April/008335.html -
very old report,
"very old report" is right. What makes
Hi,
we had a kernel panic crashing our DB server today and all libpq clients (C and
Perl clients) got stuck in poll() for hours even after the server was back up,
i.e. longer than the tcp timeout should be:
#0 0x2b2283b31c8f in poll () from /lib/libc.so.6
#1 0x2b228446f4af in PQmble
Tom Lane schrieb:
Marinos Yannikos writes:
"i_a" btree (a)
"i_ab" btree (a, b)
I suspect that these indexes are exactly the same size --- look at
pg_class.relpages or use the pg_relation_size() function to verify.
For some reason, the first one is actually about t
Recent versions of PostgreSQL seem to prefer 2d indexes somehow:
for a table "foo" with
"i_a" btree (a)
"i_ab" btree (a, b)
SELECT * FROM foo WHERE a=123
will often use "i_ab" and not "i_a" (even right after ANALYZE). This
raises some questions:
- is there even any benefit in still having bot
Hi,
when a warm standby "slave" database is being maintained, what is the
best way to keep the WAL archive files from cluttering up the disk?
According to
http://www.postgresql.org/docs/8.2/interactive/warm-standby.html it
seems to me that one could either initiate periodic backups (stop PITR
ittle overhead.
This was the original thread:
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php
Thanks,
-mjy
--
Dipl.-Ing. Marinos Yannikos, CEO
Preisvergleich Internet Services AG
Obere Donaustrasse 63, A-1020 Wien
Tel./Fax: (+431) 5811609-52/-55
Handelsgericht Wien - FN 19
