Hi,
i have some questions regarding
- behavior of vacuum and autovacuum after changing configuration and
- interaction between those two
i change the vacuum_cost_delay parameter to 0 in postgresql.conf and
reloaded the server (sighup). does that have an immediate effect on running
vaccuums and au
On Wed, 2010-01-20 at 10:04 -0600, Kevin Grittner wrote:
> I just noticed that the list has not been copied on most of this
> exchange. Please keep the list copied, as others are likely to
> contribute useful ideas.
>
> Renato Oliveira wrote:
>
> > Can I ask few questions about it, if possibl
Hi all;
is there a system catalog query or function that will show me the last time an
insert or update occurred for a specified table ?
Thanks in advance
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
Ray Stell wrote:
>> The machine had bad RAM; we were getting undetected/uncorrected single-bit
>> errors creeping through!
> who's the machine/memory vendor?
I don't know exactly; it's a colocated machine that we don't own.
dmidecode (trimmed down) says:
System Information
Manufacturer
On Wed, Jan 20, 2010 at 10:10:26AM -0500, David F. Skoll wrote:
> The machine had bad RAM; we were getting undetected/uncorrected single-bit
> errors creeping through!
who's the machine/memory vendor?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your sub
I just noticed that the list has not been copied on most of this
exchange. Please keep the list copied, as others are likely to
contribute useful ideas.
Renato Oliveira wrote:
> Can I ask few questions about it, if possible?
Sure. Please keep it "on list", though.
> We are running Linux
Hi,
Back in October 2009, I reported on strange warm-standby problems in
this thread: http://archives.postgresql.org/pgsql-admin/2009-10/msg00170.php
Just in case anyone still cares or is wondering, we found the problem.
The machine had bad RAM; we were getting undetected/uncorrected single-bit
On Wed, Jan 20, 2010 at 6:48 AM, Kevin Grittner wrote:
> Renato Oliveira wrote:
>
> > I can't implement PITR right now on our live systems, for
> > commercial reasons.
>
> What do you mean? Most of your email seems to describe techniques
> very much like PITR; why would that be OK but the exist
Renato Oliveira wrote:
> I can't implement PITR right now on our live systems, for
> commercial reasons.
What do you mean? Most of your email seems to describe techniques
very much like PITR; why would that be OK but the existing, tested
PITR not be OK? It's hard to know what to suggest with
Renato Oliveira wrote:
> Dear all,
>
> I have been thinking about PostgreSQL backup for some time now.
>
> I can't implement PITR right now on our live systems, for commercial
> reasons.
I think you need to rethink this one...
> 4 - Backup instead of time use transactionID Do a full backup, mar
Dear all,
I have been thinking about PostgreSQL backup for some time now.
I can't implement PITR right now on our live systems, for commercial reasons.
I have been backing up the server with PG_DUMP every two days, reason it takes
some times more than 24 Hours to backup the full database.
I h
11 matches
Mail list logo