hello to all
i am stuck in the following situation. i have a table which is 500GB. due to
some deleted rows the actual size is about 350-400GB and i would like to
reclaim that disk space since from now on this table will remain at this
level (350-400GB). the system is in production but the specifi
hello to all,
i have tried pg_upgrade to upgrade from 8.4 to 9.0. the operation was
completed succesfully. i only have one question:
i did the procedure twice. once without the 'link (-k) option' and one with
it. obviously the attempt with the link option was much faster. but, what
does link mean
dear all,
i would like your help on the following matter:
the other day i had to bring up the failover server. it was in warm standby
mode and everything went fine. my question is this-> when the secondary
becomes primary is there a way for the primary to immediately turn to
warm-standby mode? i
hello to all,
i am facing an issue concerning cancelled queries made on a hot standby
server. if we suppose that there are some tables that are never changed (no
inserts/updates/deletes) and that autovacuum is set to false for these
tables, what else could there be affecting these tables and conse
thanks a lot. the way it works is crystal clear to me now
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/cancelled-queries-on-standby-tp4994025p4995933.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql
is it possible that the timestamp that you put there ('2011-12-22
07:27:08') is before the time that you issued the command pg_stop_backup?
you can check that by looking at the backup.label file where is says when
the backup was finished.
you can only use point in time recovery after the point whe
you are right. my bad :)
On Thu, Dec 22, 2011 at 3:32 PM, Jerry Sievers wrote:
> MirrorX writes:
>
> > is it possible that the timestamp that you put there ('2011-12-22
> 07:27:08') is before the time that you issued the
> > command pg_stop_backup? you c
good morning to all and happy new year!
i am facing the following situation; there is a server which is using 2-5GB
of swap very often (almost all the time) and i cannot figure out why. i can
provide any information you find useful and i will start what i think is
more relevant to my 'problem'.
-
thx a lot for your reply.
i think it is measured in GB
*free*
total used free sharedbuffers cached
Mem: 65992668 644259241566744 0 196932 62767468
-/+ buffers/cache:1461524 64531144
Swap: 335544242105664 31448760
*top
thx a lot for your advice. it's true that even under load, i havent seen any
so or si...so probably it's best to let the OS handle the situation.
in the meantime if anyone has any idea why the OS would do such a thing, pls
share it with us.
thx
--
View this message in context:
http://postgre
i dont quite understand the question. could you pls clarify a little?
you want to save the pg_xlog-files from where? the master of the slave?
the tool you are looking for, if it exists, should do what?
thx
On Sun, Mar 11, 2012 at 11:05 PM, Martin von Oertzen [via PostgreSQL] <
ml-node+s1045698n5
dear all,
i have come to face the following situation:
-initially the server was 8.4.7
-i used pg_upgrade --link so that the upgrade would be quick
-i created a new tablespace with the intention of moving all the indexes
there (different partition)
-when issueing a statement like 'alter index xxx
12 matches
Mail list logo