The problem is, the DB keeps on printing these entries the whole day and
bloats the log file. It's 11AM now and already 14,700 entries of this
message in the log and it keeps on increasing. What needs to be done to
counter this unnecessary logging? This machine will be the production
secondary DB a
Awesome! Thanks Bob.
On Tue, 2011-04-19 at 12:51 -0700, Bob Lunney wrote:
>
> Slony will use any unique index on a table for replication purposes, so the
> list of tables should come from:
>
> select relname
> from pg_class c
> join pg_namespace n on c.relnamespace = n.oid
> where nspname
--- On Tue, 4/19/11, Jerry Sievers wrote:
> From: Jerry Sievers
> Subject: Re: [ADMIN] PKs without indexes
> To: jweatherma...@alumni.wfu.edu
> Cc: pgsql-admin@postgresql.org
> Date: Tuesday, April 19, 2011, 11:19 AM
> John P Weatherman
> writes:
>
> > Hi all,
> >
> > I am attempting to set u
On 04/19/2011 02:11 PM, Ray Stell wrote:
On Tue, Apr 19, 2011 at 11:16:08AM +0200, rudi wrote:
On 04/19/2011 10:09 AM, Gerhard Hintermayer wrote:
So you keep the old pg_xlog
the admin book says to exclude old pg_xlog
Which book is this?
So I guess something like this (from new master to fo
John P Weatherman writes:
> Hi all,
>
> I am attempting to set up slony-i and have run into a minor
> glitch...apparently whoever designed the database I have inherited
> didn't consistently build indexes to go along with Primary Keys, or at
> least that's the error message I have been getting.
John P Weatherman writes:
> I am attempting to set up slony-i and have run into a minor
> glitch...apparently whoever designed the database I have inherited
> didn't consistently build indexes to go along with Primary Keys, or at
> least that's the error message I have been getting. I am far from
Selva manickaraja wrote:
> We encountered this for the 3rd time after completing a PITR.
> 2011-04-19 12:12:59 MYT LOG: autovacuum: found orphan temp table
> "pg_temp_108"."session_id" in database "np"
> [for many different temp tables]
> Anyone has any idea why this is happening?
There
Muruganand Karthikeyan wrote:
> Yes it has to be version 8.4.5, since we have already upgraded at
> an organizational level to 8.4.4, so the next obvious upgrade
> would be to 8.4.5:)
Actually, the next obvious upgrade at this moment would be to 8.4.8,
unless you feel a need to give each b
On Tue, Apr 19, 2011 at 11:16:08AM +0200, rudi wrote:
> On 04/19/2011 10:09 AM, Gerhard Hintermayer wrote:
> So you keep the old pg_xlog
the admin book says to exclude old pg_xlog
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.
Στις Tuesday 19 April 2011 13:11:35 ο/η Alessio Gennari έγραψε:
> Hello to everyone,
> where Can I find PL/Java installation manual and/or tutorials?
>
> Thanks in advance.
>
Here : http://pgfoundry.org/projects/pljava/ and here :
http://wiki.tada.se/index.php?title=Main_Page
> Alessio
>
-
Hi all,
I am attempting to set up slony-i and have run into a minor
glitch...apparently whoever designed the database I have inherited
didn't consistently build indexes to go along with Primary Keys, or at
least that's the error message I have been getting. I am far from
confident in my own sqlfu
Thank you very much.
On 19 April 2011 12:38, raghu ram wrote:
>
>
> On Tue, Apr 19, 2011 at 3:41 PM, Alessio Gennari <
> alessio.gennar...@gmail.com> wrote:
>
>> Hello to everyone,
>> where Can I find PL/Java installation manual and/or tutorials?
>>
>
> Below link will demonstrates the PL/java i
On Tue, Apr 19, 2011 at 3:41 PM, Alessio Gennari <
alessio.gennar...@gmail.com> wrote:
> Hello to everyone,
> where Can I find PL/Java installation manual and/or tutorials?
>
Below link will demonstrates the PL/java installation on Opensuse::
http://www.banym.de/projects/adempiere/howtos/instal
Hello to everyone,
where Can I find PL/Java installation manual and/or tutorials?
Thanks in advance.
Alessio
On Tue, 2011-04-19 at 12:38 +0530, Muruganand Karthikeyan wrote:
>
> Yes it has to be version 8.4.5, since we have already upgraded at an
> organizational level to 8.4.4, so the next obvious upgrade would be to
> 8.4.5:)
This is not the right path, IMHO.
--
Devrim GÜNDÜZ
Principal Systems E
I also streaming replication _and_ ship WALs them to the slaves, something
like: restore_command='rsync -pog master::postgresql-wals/%f %p', so
normally the slaves are up to date (via streaming replication) and the WALs
are also on the slaves to be able to recover (maybe to some PIT) from them
in c
On 04/19/2011 10:09 AM, Gerhard Hintermayer wrote:
assuming you have configured rsyncd on the server as:
[postgresql-data]
uid = postgres
path = /var/lib/postgresql/9.0/data
comment = PostgreSQL 9.0 data dir
exclude = postmaster.log pg_xlog/* postmaster.pid postgresql.conf
Did you run ./initidb with /usr/local/pgsql/bin/ as your current
directory?
Is there a postgres executable in that directory? @: yes there is a postgres in
that directory.
Also, what version? @: 9.0.1
Where did you get it?@: by compiling the source code.
How did you install it? @: above.
Dear All,
We encountered this for the 3rd time after completing a PITR.
The database starts up as usual and we could carry out the read and write
transactions. After a while the following errors start appearing in the log.
So we tried running vacuumdb with options All,Freeze,Analyze to see if tha
Hi, I do rsync -a --delete new_primary_server::postgresql-data/
/var/lib/postgresql/9.0/data/
Take care to use -a, I had -r and wondered, why the rsync took so long,
despite the data was nearly the same.
assuming you have configured rsyncd on the server as:
[postgresql-data]
uid = postgres
Hi,
I've setup streaming replication + file-based log-shipping, with a
hot-standby.
Everything's good, except I don't know which is the correct way to sync
the once-master db with the newly promoted master after a switchover,
1) I shutdown the master and touch the trigger_file on the slave.
> Is there any reason it has to be 8.4.5? As it seems 8.4.4 is available.
>
Thanks to Philippe for the link:
ftp://ftp-archives.postgresql.org/pub/source/v8.4.5/
Yes it has to be version 8.4.5, since we have already upgraded at an
organizational level to 8.4.4, so the next obvious upgrade would b
22 matches
Mail list logo
