Hi,
Below command has been running since ~700 minutes in one of our
PostgreSQL servers.
DELETE FROM mugpsreglog
WHERE NOT EXISTS (SELECT 1
FROM mueventlog
WHERE mueventlog.eventlogid =
mugpsreglog.eventlogid);
Seq Scan on mugps
Joshua Shanks wrote:
>> - Have you changed the random page cost on either installation?
>
> This is whatever the default is for both boxes (commented config file says
> 4.0)
>
>> - Have both installations had VACUUM ANALYZE run recently?
>
> This is the first thing I did and didn't seem to do a
> - Have you changed the random page cost on either installation?
This is whatever the default is for both boxes (commented config file says 4.0)
> - Have both installations had VACUUM ANALYZE run recently?
This is the first thing I did and didn't seem to do anything.
Oddly enough I just went a
Joshua Shanks wrote:
> This query is run on a test system just after a backup of the database
> has been restored and it does exactly what I expect it to do
[snip]
Obvious questions:
- Have you changed the random page cost on either installation?
- Have both installations had VACUUM ANALYZE run
On Wed, Aug 6, 2008 at 6:12 PM, dforum <[EMAIL PROTECTED]> wrote:
> Hello to all,
>
>
> I have a Linux 2.6.24.2--std-ipv4-64 #3 SMP Tue Feb 12 12:27:47 CET 2008
> x86_64 Intel(R) Xeon(R) CPU X5355 @ 2.66GHz GenuineIntel GNU/Linux
> with 8Gb of memory. Using sata II disk in RAID 1 (I known that
Gregory S. Youngblood wrote:
From: Mark Kirkwood [mailto:[EMAIL PROTECTED]
Mark Wong wrote:
On Mon, Aug 4, 2008 at 10:56 PM, Gregory S. Youngblood
<[EMAIL PROTECTED]> wrote:
I recently ran some tests on Ubuntu Hardy Server (Linux) comparing
JFS, XFS,
and ZFS+FU
Hello to all,
I have a Linux 2.6.24.2--std-ipv4-64 #3 SMP Tue Feb 12 12:27:47 CET
2008 x86_64 Intel(R) Xeon(R) CPU X5355 @ 2.66GHz GenuineIntel GNU/Linux
with 8Gb of memory. Using sata II disk in RAID 1 (I known that is bad,
but it would change has quickly I can).
I have a database of 38
This query is run on a test system just after a backup of the database
has been restored and it does exactly what I expect it to do
EXPLAIN ANALYZE SELECT foos.* FROM foos INNER JOIN bars ON foos.id =
bars.foos_id WHERE ((bars.bars_id = 12345)) ORDER BY attr1 LIMIT 3
OFFSET 0;
QUERY PLAN
---
Marcin Citowicki wrote:
Hello,
I forgot to add - all those 'out of memory' errors happen when backup db
is trying to create index. Every 'CREATE INDEX' operation is followed by
'out of memory' error.
are you sure that your OS (or ulimit) is able to support a
maintenance_work_setting that la
Hello
you have some data files broken.
try to use http://svana.org/kleptog/pgsql/pgfsck.html - but DO
DATABASE CLUSTER FILES BACKUP BEFORE. pgfsck doesn't support 8.3, but
it can help you to search currupted rows. Then you have remove these
rows, thats all. Later check your hardware - probably yo
Hello,
I forgot to add - all those 'out of memory' errors happen when backup db
is trying to create index. Every 'CREATE INDEX' operation is followed by
'out of memory' error.
Thanks!
Marcin
Marcin Citowicki wrote:
Hello,
We have a bit of a problem with the daily db backup. At the moment
Hello,
We have a bit of a problem with the daily db backup. At the moment the
backup db size is half of the main db, and we have the following errors
in the log file:
ERROR: out of memory
DETAIL: Failed on request of size 536870912
(There's a bunch of those.)
There were some 'permission den
12 matches
Mail list logo
