ib/postgresql/8.4/main" -o "-p 5432
-c autovacuum=off -c autovacuum_freeze_max_age=20" start >>
"/tmp/logging_pgupgrade" 2>&1
pg_ctl failed to start the old server
Failure, exiting
Now, the 8.4 cluster actually does get started by the above pg_
dbname=postgres port=%s connect_timeout=5
host=localhost", portstr);
for (i = 0; i < wait_seconds; i++)
{
Happy new year!
--
Alexander Fortin
http://about.me/alexanderfortin/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
htt
7;t hesitate ;)
Thanks for your time
[1]
http://www.postgresql.org/docs/9.1/static/monitoring-stats.html#MONITORING-STATS-VIEWS
--
Alexander Fortin
http://about.me/alexanderfortin/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
licas.
By the way, maybe you know where I could find documentation about
possible values from column "state" on view pg_stat_replication? I can
see "streaming" when everything is ok, and once I could get just a
"catchup" while a replica was synching.
in/base
replica:
37G /var/lib/postgresql/9.1/main/base/
Does pg_database_size() return size occupied by indexes too? If not, the
difference could be due to index space I guess.
Thanks!
--
Alexander Fortin
http://about.me/alexanderfortin/
--
Sent via pgsql-admin mailing list (pgsql-
On 3/29/12 11:41 AM, Raghavendra wrote:
> Can you also tell what replication is in place ?
Sure thing, it's Postgresql 9.1.2, master + two replicas in streaming
replication hot standby
--
Alexander Fortin
http://about.me/alexanderfortin/
--
Sent via pgsql-admin mailing lis
On 3/29/12 3:24 PM, Bernhard Schrader wrote:
> Hi,
>
> which filesystem do you use, and which kernel is running?
Hi Bernhard,
it's XFS on Ubuntu server 11.10, Kernel is 3.0.0-16-virtual (m1.large
Ec2 instances)
--
Alexander Fortin
http://about.me/alexanderfortin/
--
Sent v
% Mounted on
/dev/md_d0128G 36G 93G 28% /var/lib/postgresql
so, with Postgres shut down, numbers get back to make sense to me.
--
Alexander Fortin
http://about.me/alexanderfortin/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to
standing, it's logrotate that does the job, given
that the package postgresql-common creates an entry for daily
/var/log/postgresql/*.log rotation.
As for the archive_command, no, it's defaulted to empty:
#archive_command = ''
--
Alexander Fortin
http://about.me/alexanderfortin/
--
learly that
it's definitely unrelated to Postgres (apparently seems that I can
reproduce the change of data occupation on the XFS file system just
accessing those files).
Talk soon,
--
Alexander Fortin
http://about.me/alexanderfortin/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgre
10 matches
Mail list logo