On Mon, Jul 24, 2006 at 08:43:15AM +1000, Mark Matthews wrote:
> Can anyone recommend good reference text, web or other, for general
> PostgreSQL DBA tasks.
The PostgreSQL documentation is a good place to start. See "Server
Administration," especially the chapters concerning routine maintenance
Hello friend,
Well, I have not a tutorial at hand now, but i can say to you some
tasks i remember, and these can make you spent a long time learning
about how to do.
I think that the tasks essentially you must to know are:
- Install database
- Configure the two most important files (pg_hba.conf
Hello,
Can anyone recommend good reference text, web or other, for general
PostgreSQL DBA tasks.
Stuff like:
* Things to do to clean up periodically (CLUSTER, VACUUM FULL, etc)
* How to analyse queries to optimise data retrieval (Use of EXPLAIN,
etc)
* etc ...
We are running Debian stable
I am running 8.1.4 on Windows.
Quick question - I assume CLUSTER will lock the tables, correct?
In my scenario where the number of live rows is very small but the
number of dead rows is huge, how long will tis take?
I have a problem in that this database is a live monitoring system which
I cannot
Hello,
I see some OS files (50+ GB total) but cannot see
anything in psql -l.
There seem to be some big tables there.
I wonder if there are some tools that would dump the
tables in text.
or, how to make PostgreSQL "connect" to these files
again?
Thanks in advance!
psql -V
psql (PostgreSQL) 7.2.
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Benjamin Krajmalnik wrote:
>> What can be causing this growth? Not vacuuming often enough?
> The is exactly the reason.
>> I hav
>> pg_autovacuum running every 60 seconds. These tables have 10-15
>> insert/update statements per second.
> You shoul
After a long battle with technology, [EMAIL PROTECTED] ("Benjamin Krajmalnik"),
an earthling, wrote:
> Any assistance or guidance will be deeply appreciated. I am pulling
> hairs on this one.
It needs to be vacuumed a lot more aggressively. If you're using
pg_autovacuum, the defaults seem to be
Hi,
On Sun, 23 Jul 2006, Benjamin Krajmalnik wrote:
The actual number of physical rows in this table is 3404. Row width is
361. Table size = 639 MB.
What can be causing this growth? Not vacuuming often enough? I hav
pg_autovacuum running every 60 seconds. These tables have 10-15
insert/upda
Benjamin Krajmalnik wrote:
> What can be causing this growth? Not vacuuming often enough?
The is exactly the reason.
> I hav
> pg_autovacuum running every 60 seconds. These tables have 10-15
> insert/update statements per second.
You should probably run VACUUM FULL to get the table back to a
This is subsequent to the previous issue which I am expperiencing.
In my monitoring application, I have a few tables which contain few rows
but are constantly pounded with updates.
These tables are growing at very high rates. For example, a table with
less than 4K rows, which when reloaded was ab
10 matches
Mail list logo