hi
2016-08-04 16:19 GMT+03:00 Ian Barwick :
> Hi
>
> On 08/04/2016 05:57 PM, Pekka Rinne wrote:
>
>> hi!
>>
>> I have been using postgres 9.4 and repmgr2.0 combination and been doing
>> replication (hot standby). Now I'd like to start doing slot based
>> replication and
On Tue, Aug 16, 2016 at 1:10 PM James Sewell
wrote:
> Hey,
>
> I understand that.
>
> But a hot standby should always be ready to promote (given it originally
> caught up) right?
>
> I think it's a moot point really as some sort of corruption has been
> introduced, the
Hey,
I understand that.
But a hot standby should always be ready to promote (given it originally
caught up) right?
I think it's a moot point really as some sort of corruption has been
introduced, the machines still won't wouldn't start after they could see
the archive destination again.
Just wondering what the end goal is for this project... Is it to just
maintain an up to date Postgres fork that will compile with a C++ compiler?
Is it to get a conversation going for a direction for Postgres itself to
move? The former I don't see gaining much traction or doing all that much
for
On 8/15/2016 7:23 PM, James Sewell wrote:
Those are all good questions.
Essentially this is a situation where DR is network separated from
Prod - so I would expect the archive command to fail. I'll have to
check the script it must not be passing the error back through to
PostgreSQL.
This
Those are all good questions.
Essentially this is a situation where DR is network separated from Prod -
so I would expect the archive command to fail. I'll have to check the
script it must not be passing the error back through to PostgreSQL.
This still shouldn't cause database corruption though
On Sat, Aug 13, 2016 at 12:41 AM, Jeff Janes wrote:
> On Wed, Aug 10, 2016 at 11:06 PM, Yelai, Ramkumar
> wrote:
>> At present, I have some requirement to truncate the data base to reclaim
>> disk space and at the same time I need to take
On 08/15/2016 01:59 PM, Edmundo Robles wrote:
Please do not top post:
https://en.wikipedia.org/wiki/Posting_style
The preferred style is bottom or interleaved as it makes the thread
easier to follow
Adrian i have hosted in a rackspace a Debian 7 with 2G RAM.
I assume that would be one
Adrian i have hosted in a rackspace a Debian 7 with 2G RAM.
John, the table have 8 constraints and 5 indexes.
Ilya thanks for the tip, i will search about OLTP.
On Mon, Aug 15, 2016 at 3:47 PM, Ilya Kazakevich <
ilya.kazakev...@jetbrains.com> wrote:
> Hello.
>
>
>
> From:
>
>
Hello.
From:
http://www.pgpool.net/
pgpool-II also has a limit on the maximum number of connections, but extra
connections will be queued instead of returning an error immediately.
But your configuration does not look optimal for me. Here are some things you
may try:
1) Get rid
On 08/15/2016 01:30 PM, Edmundo Robles wrote:
Hi!
I want find a software to 'enqueue' the client connections to database,
so if i reach the max limit the query must be holding in a queue until
one connection is released.
I have many devices (100+) saving their state to a database, each
On 8/15/2016 1:30 PM, Edmundo Robles wrote:
I want find a software to 'enqueue' the client connections to
database, so if i reach the max limit the query must be holding in a
queue until one connection is released.
pgbouncer is the correct answer, you may need to play about with the
On Mon, Aug 15, 2016 at 3:56 PM, Bruce Momjian wrote:
> On Mon, Aug 15, 2016 at 12:18:04PM -0700, Adrian Klaver wrote:
> > https://www.postgresql.org/docs/9.5/static/pgupgrade.html
> >
> > "Obviously, no one should be accessing the clusters during the upgrade.
> > pg_upgrade
Hi!
I want find a software to 'enqueue' the client connections to database, so
if i reach the max limit the query must be holding in a queue until one
connection is released.
I have many devices (100+) saving their state to a database, each
minute, but the table is too large more than
On Mon, Aug 15, 2016 at 12:18:04PM -0700, Adrian Klaver wrote:
> https://www.postgresql.org/docs/9.5/static/pgupgrade.html
>
> "Obviously, no one should be accessing the clusters during the upgrade.
> pg_upgrade defaults to running servers on port 50432 to avoid unintended
> client connections.
On 08/15/2016 11:52 AM, Pete Fuller wrote:
Same chips, same model Dell Poweredge actually. The process is pretty
much the same between the local and offsite replicas, we have a
home-brew script that runs an rsync from the master to the replica. On
the local replica, it then takes the machine
Same chips, same model Dell Poweredge actually. The process is pretty much the
same between the local and offsite replicas, we have a home-brew script that
runs an rsync from the master to the replica. On the local replica, it then
takes the machine out of pacemaker standby, on the offsite
On 08/15/2016 08:04 AM, Pete Fuller wrote:
We have not found any obvious differences, other than the size of the
databases (~ 100 gig on the testing site vs 400 Gig in production). In
fact, the upgrade path seems to work with our production db when testing
on our offsite replica that lives in
Hello,
On Mon, 2016-08-15 at 08:45 -0700, Adrian Klaver wrote:
> On 08/15/2016 08:04 AM, Pete Fuller wrote:
> >
> > We have not found any obvious differences, other than the size of
> > the
> > databases (~ 100 gig on the testing site vs 400 Gig in
> > production). In
> > fact, the upgrade path
On Sun, Aug 14, 2016 at 9:33 PM, zh1029 wrote:
> Hi,
> We are using PostgreSQL 9.3.11. We are observing DB update failed due to
> lock timeout. failure because waiting for RowExclusiveLock. Autovacuum uses
> plain vacuum which uses ShareUpdateExclusiveLock. right?
> But from
On Thu, Aug 11, 2016 at 10:39 PM, James Sewell
wrote:
> Hello,
>
> We recently experienced a critical failure when failing to a DR
> environment.
>
> This is in the following environment:
>
>
>- 3 x PostgreSQL machines in Prod in a sync replication cluster
>- 3
On 08/15/2016 08:04 AM, Pete Fuller wrote:
We have not found any obvious differences, other than the size of the
databases (~ 100 gig on the testing site vs 400 Gig in production). In
fact, the upgrade path seems to work with our production db when testing
on our offsite replica that lives in
On 08/15/2016 08:05 AM, Ioana Danes wrote:
On Mon, Aug 15, 2016 at 10:52 AM, Adrian Klaver
> wrote:
They are not the same servers but they have similar setup.
Fortunately
they are qa and development.
On Mon, Aug 15, 2016 at 10:52 AM, Adrian Klaver
wrote:
> On 08/15/2016 07:40 AM, Ioana Danes wrote:
>
>> Hello Adrian,
>>
>> On Mon, Aug 15, 2016 at 10:00 AM, Adrian Klaver
>> > wrote:
>>
>> On 08/15/2016
We have not found any obvious differences, other than the size of the databases
(~ 100 gig on the testing site vs 400 Gig in production). In fact, the upgrade
path seems to work with our production db when testing on our offsite replica
that lives in our backup datacenter, near identical
On 08/15/2016 07:40 AM, Pete Fuller wrote:
Directories are correct. We do not utilize tablespaces.
Anything obviously different in the setup between your production
servers and the testing and development clusters?
On Aug 15, 2016, at 10:06 AM, Adrian Klaver
On 08/15/2016 07:40 AM, Ioana Danes wrote:
Hello Adrian,
On Mon, Aug 15, 2016 at 10:00 AM, Adrian Klaver
> wrote:
On 08/15/2016 06:48 AM, Ioana Danes wrote:
Hello All,
I am running postgres 9.4.8 on centos 7 and
Directories are correct. We do not utilize tablespaces.
> On Aug 15, 2016, at 10:06 AM, Adrian Klaver wrote:
>
> On 08/15/2016 06:20 AM, Pete Fuller wrote:
>> Hello all,
>>
>> We are attempting to upgrade a production 9.2 postgres cluster to 9.5. The
>> server
Hello Adrian,
On Mon, Aug 15, 2016 at 10:00 AM, Adrian Klaver
wrote:
> On 08/15/2016 06:48 AM, Ioana Danes wrote:
>
>> Hello All,
>>
>> I am running postgres 9.4.8 on centos 7 and few days ago I started to
>> get this error MultiXactId 32766 has not been created yet
On 08/15/2016 06:20 AM, Pete Fuller wrote:
Hello all,
We are attempting to upgrade a production 9.2 postgres cluster to 9.5. The
server is running Centos 7 with the Centos version - currently 9.2.15 We are
installing the postgresql provided rpm of postgresql9.5 from the postgresql
repo,
On 08/15/2016 06:48 AM, Ioana Danes wrote:
Hello All,
I am running postgres 9.4.8 on centos 7 and few days ago I started to
get this error MultiXactId 32766 has not been created yet -- apparent
wraparound in 2 instances.
1. On one database server during the nightly task that does the "vacuum
Hello All,
I am running postgres 9.4.8 on centos 7 and few days ago I started to get
this error MultiXactId 32766 has not been created yet -- apparent
wraparound in 2 instances.
1. On one database server during the nightly task that does the "vacuum
analyze". I upgraded to postgres 9.4.9 as
On Mon, Aug 15, 2016 at 9:27 AM, Михаил wrote:
> Hi!
>
> I need to escape double quotes only:
> test=# select regexp_replace('"""{Performer,"Boomwacker ""a""
> Recording""}"""', '([^"])"{2}([^"])', '\1\"\2', 'g');
> regexp_replace
>
On Mon, Aug 15, 2016 at 06:27:06PM +0500, Михаил wrote:
> I need to escape double quotes only:
> test=# select regexp_replace('"""{Performer,"Boomwacker ""a""
> Recording""}"""', '([^"])"{2}([^"])', '\1\"\2', 'g');
> regexp_replace
>
Hi!
I need to escape double quotes only:
test=# select regexp_replace('"""{Performer,"Boomwacker ""a""
Recording""}"""', '([^"])"{2}([^"])', '\1\"\2', 'g');
regexp_replace
-
"""{Performer,"Boomwacker \"a"" Recording\"}"""
This is
Hello all,
We are attempting to upgrade a production 9.2 postgres cluster to 9.5. The
server is running Centos 7 with the Centos version - currently 9.2.15 We are
installing the postgresql provided rpm of postgresql9.5 from the postgresql
repo, currently 9.5.4. In testing and on our
36 matches
Mail list logo