YZE should run each 2.5-3 hours.
If it does not proceed, check that you do not have some process still doing
manual maintenance or DDL on those tables, they might lock the table and kill
autovacuum
(check the pg_stat_activity, and set log_autovacuum_min_duration=0 to track
all job done by a
with previous
> changes. Did we do something wrong ?
Everything is relative to the size of the table, what is the content of
pg_class for the second kind of tables ? (relpages/reltuples)
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation
signature.asc
Description: This is a digitally signed message part.
:
*
http://archives.postgresql.org/message-id/201209221857.44568.and...@2ndquadrant.com
*
http://archives.postgresql.org/message-id/201209150233.25616.and...@2ndquadrant.com
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation
:
*
http://archives.postgresql.org/message-id/201209221857.44568.and...@2ndquadrant.com
*
http://archives.postgresql.org/message-id/201209150233.25616.and...@2ndquadrant.com
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation
r
> edited and "beautified." I want something I can print and hang on the wall
> as a reference document for developers writing code and SQL.
postgresql_autodoc is old and simple, and works (even for complex database).
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadran
) and compare with the rsync
with --ignore-time instead of --checksum
That should give a good idea on the extra cost of the block checksum
for files without changes (which are matched by --checksum).
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Dévelo
-progress can be informative...
>
> --
> Scott Ribe
> scott_r...@elevated-dev.com
> http://www.elevated-dev.com/
> (303) 722-0567 voice
>
>
>
>
>
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
keep --owner --group --perms --recursive
(or you do file by file with a find or something like that ?)
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To mak
should not happen. As many things should not happen...
If you want to reduce the re-rsync step, you may want to try to have
similar files in both places by using vacuum freeze before initial
rsync, or something like that (so hint bits are set before rsync).
--
Cédric Villemain +33 (0)6 20 30 22
2011/11/15 Scott Ribe :
> On Nov 15, 2011, at 3:02 AM, Cédric Villemain wrote:
>
>> no, you are wrong.
>> -c, --checksum
>> "This changes the way rsync checks if the files have been changed and
>> are in need of a transfer. Without this option, rsync uses
file that has a
matching size. Generating the checksums means that both sides will
expend a lot of disk I/O reading all the data in the files in the
transfer (and this is prior to any reading that will be done to
transfer changed files), so this can slow things down significantly. "
...
--
Cédr
rsyncing all data from new master to new slave.
>
>
> Tomorrow, I shall try with PG9.0.3, 3 slaves and a primary database with 100
> GB.
>
> Thanks.
>
> Jal
just for the value : rsync --checksum is the option to use to prevent
copying of identical files (it computes checksum
ce Software Center
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développ
2011/7/20 Tom Lane :
> Ken Caruso writes:
>> On Sun, Jul 17, 2011 at 3:04 AM, Cédric Villemain <
>> cedric.villemain.deb...@gmail.com> wrote:
>>>> Block number 12125253 is bigger that any block we can find in
>>>> base/2651908/652397108.1
>
>&g
3 is bigger that any block we can find in
base/2651908/652397108.1
Should the table size be in the 100GB range or 2-3 GB range ?
This should help decide: if in the former case, then probably at least
a segment disappear or, in the later, the shared_buffer turn
corrupted.
Ken, you didn't cha
://www.postgresql.org/docs/9.1/static/queries-with.html
7.8.2. Data-Modifying Statements in WITH
And delete/insert in the same query.
Else there is no special feature to limit the number of rows in a table
>
> Thanks.
--
Cédric Villemain 2ndQuadrant
http://2ndQua
2011/5/3 Merlin Moncure :
> On Tue, May 3, 2011 at 8:55 AM, Cédric Villemain
> wrote:
>> 2011/5/3 Merlin Moncure :
>>>
>>> no it will not, or at least there is no guarantee it will be. the
>>> only way to reset the buffers in that sense is to restart the
ven then they might not be read from disk, because they could
> sit in the o/s cache). to force a read from the drive you'd have to
> reboot the server, or at least shut it down and use a lot of memory
> for some other purpose.
with linux, you can : "echo 3 > /proc/sys/vm/drop_cache
2011/4/22 Mario Splivalo :
> On 04/22/2011 03:20 PM, Cédric Villemain wrote:
>>
>> 2011/4/21 raghu ram:
>>>>
>>>> Heh, I've neglected to mention that i'm using postgres 8.4.5 on Debian
>>>> Stable. Is there a way to reset statistics
s in PG 8.4 at cluster level. Can
> anybody has the information ?
> -- Raghu
With 8.4 you only have the pg_stat_reset(), it resets all stats. The
finest one in 9.0 is a new feature/improvement.
See http://www.postgresql.org/docs/8.4/static/monitoring-stats.html
--
Cédric Villemain
ake over if
> necessary.
>
We have some work in progress in repmgr for that. And it offers
stronger choice when you have several standby and want to pick the
most up to date to become a new master.
--
Cédric Villemain 2ndQuadrant
http://2ndQuadrant.fr/ PostgreSQL : Exper
>
>
>>
>> How can I accomplish this ?
>> Thanks
>> Bala
>> ________
>> The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with
>> Hotmail. Get busy.
>
--
Cédric Villemain 2ndQuadrant
http:
unter http://portal.gmx.net/de/go/maxdome01
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
--
Cédric Villemain
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
2010/4/22 Achilleas Mantzios :
> Στις Thursday 22 April 2010 16:53:05 ο/η Cédric Villemain έγραψε:
>> 2010/4/22 Achilleas Mantzios :
>> > Hello,
>> > i have this serious problem in one of our remote vessels. (comm is done by
>> > minicom to the remote satelite
: Succeeded.
>
> Is there anything i can do to savage the situation?
>
> (one of) the hard part here is that i dont have neither physical nor network
> access to the server
> (only ultra expensive unreliable satellite comms)
>
> Thanks for any hints...
>
> --
> A
to handle postgresql plugins.
(very simple and usefull)
But I wonder if it is really interesting : you will have the most bloated
table reduce to the less bloated table after vacuuming, probably.
I prefer graph specific relations and just alert me if some relation is bloated
too much.
>
ecksum :
sudo su -s /bin/bash - zabbix
sudo -u postgres /usr/local/share/zabbix/check_postgres.pl --db=DBNAME
- --action=settings_checksum --critical=0
Server side:
pgs :
check_postgres.pl output simple
pgs[ACTION,DBNAME]
pgm :
check_postgres.pl output mrtg
pgs[ACTION,DBNAME,EXTRA]
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johann Spies a écrit :
> On Mon, Jan 19, 2009 at 05:10:07PM +0100, Cédric Villemain wrote:
>> Note that you have some plugins :
>>
>> * http://bucardo.org/check_postgres/ (plugin for nagios a
t; Linux/Solaris System Administrator
>
>
- --
Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53
http://dalibo.com - http://dalibo.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkl0pdoACgkQo/dppWjpEvykagCdF0BlMSfyt92XM6NUj6Ez/Nl7
E4cAn2a0
r. There
is no possible way you should be doing this as root anyway.
A
I like to suggest you (dr_pompei) to have a look at the docs about
pg_hba.conf.
Andrew, it seems "root" is here a postgresql user (which have rights to
connect to "somedb")
--
Cédric Villemain
Adminis
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53
http://dalibo.
to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53
http://dalibo.com - http://dalibo.org
begin:vcard
fn;quoted-printable:C=C3=A9dric Villemain
n;quoted-printable:Villemain;C
Hutger Hauer a écrit :
Dear all,
I'm looking for a monitoring tool that helps me to pick performance
informations (heap blocks, buffer hits, etc) about a specific PostgreSQL DB
or table, such as MRTG does.
Does someone know a tool that can provide me such information?
Have a look
t; Then you shut down the db.
>
> And rsync again, which will be faster than doing a complete move with
> shutdown.
>
> The key here is, if you use this method... there is *zero* way around
> shutting down the database before the second rsync.
>
>
> Sincerely,
st way to accomplish this? Or am i wrong in
> thinking i cannot access adta directly accross databases?
>
> Any help much apperciated.
>
> thanks gp
--
Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53
http://dalibo.com - http://dalibo.org
pgpVXWdJxDjJn.pgp
Description: PGP signature
35 matches
Mail list logo
