Thanks for all.
I will try pgpool-II & pgbouncer . Hope it is good solution.
Tuan Hoang Anh
On Wed, Jan 7, 2015 at 8:30 AM, Sameer Kumar
wrote:
>
> On 6 Jan 2015 03:02, "tuanhoanganh" wrote:
> >
> > Hello everybody
> >
> > Does anyone user pg-pool II on real production ?
>
> Yes we have a cus
Just curious. Have you checked that the tables are being vacuum/analyzed
periodically and that the statistics are up to date? Try running the
following query to verify:
SELECT n.nspname,
s.relname,
c.reltuples::bigint,
-- n_live_tup,
n_tup_ins,
n_tup_upd,
n
Yes, I'm using a customized fork of 9.1.9.
Ok, adding back spi and dummy_seclabel makes all regression tests pass.
I now have one concern though. Inspite of adding pgcrypto to the
exclude list, it still ends up being built and installed. Any way to avoid
this?
Thanks,
Deepak
On Thu, Jan 8, 2
I mixed up my email threads. I was following
http://michael.otacoo.com/postgresql-2/postgres-9-4-feature-highlight-logical-replication-protocol/
Looking back at it now, I can see that it didn't use psql to call
START_REPLICATION.
On Sat, Jan 10, 2015 at 12:39 PM, Andres Freund
wrote:
> On 2015
On Fri, Jan 9, 2015 at 7:52 PM, Tomas Vondra
wrote:
> On 9.1.2015 23:14, Michael Nolan wrote:
> > I'm running 9.3.5 on a virtual machine with 5 cores and 24 GB of
> > memory. Disk is on a SAN.
> >
> > I have a task that runs weekly that processes possibly as many as
> > 120 months worth of data,
The function is a complicated plpgsql function that makes numerous database
queries, all read-only. (Other parts of that program may make changes to
the database.)
The first database shutdown and the shutdown/reboot later on were both
'clean' shutdowns, so there shouldn't have been any kind of tra
On 2015-01-10 10:24:56 -0800, Brent Tubbs wrote:
> That's working! The blog posts I linked earlier
Which blogpost is that? At least this thread doesn't seem to contain a
reference.
> made me think that I had to explicitly call START_REPLICATION, but I
> guess that's not necessary?
START_REPLICA
On 01/09/2015 07:52 PM, Tomas Vondra wrote:
On 9.1.2015 23:14, Michael Nolan wrote:
I'm running 9.3.5 on a virtual machine with 5 cores and 24 GB of
memory. Disk is on a SAN.
I have a task that runs weekly that processes possibly as many as
120 months worth of data, one month at a time. Since
That's working! The blog posts I linked earlier made me think that I had
to explicitly call START_REPLICATION, but I guess that's not necessary?
For anyone else following this thread, I found some better examples at
http://pgci.eisentraut.org/jenkins/job/postgresql_master_world/Documentation/logi
On Sat, Jan 10, 2015 at 9:22 AM, Brent Tubbs wrote:
> psql "dbname=postgres replication=database user=postgres" -c
> "START_REPLICATION SLOT foobar LOGICAL 0/D9C59A28"
> unexpected PQresultStatus: 8
psql is not smart enough to understand that with a replication connection..
> Advice?
You should u
10 matches
Mail list logo
