I am using postgres 9.4, the default install with "brew install postgres,
no tuning at all. BTW if I use postgres.app application the benchmarks run
twice as slow!
Why do you think there is such dramatic difference between
EXECUTE 'INSERT INTO ' || quote_ident(partition_name) || ' SELECT
($1)
Michael Nolan writes:
> One of my sons was hired by Google last year after spending the past
> several years working on various open-source projects, it took 2 days of
> back-and-forth with Google's legal department before he was satisfied with
> the restrictions in their offer.
FWIW, I had a pre
The logical replication features in 9.4 look very promising as an
alternative to the binary replication that requires an identical schema on
both ends. There's no reason that the thing you're replicating to couldn't
be something like RabbitMQ or Storm.
I've been playing with a JSON-based decoder p
On 11.3.2015 21:43, Tim Uckun wrote:
> Hey I hate to bump my post but I would really appreciate some input
> on this benchmark. I am very alarmed that adding a very simple
> partitioning trigger slows the insert speed by an order of magnitude.
> Is there any way to speed this up?
I think to actual
One of my sons was hired by Google last year after spending the past
several years working on various open-source projects, it took 2 days of
back-and-forth with Google's legal department before he was satisfied with
the restrictions in their offer.
--
Mike Nolan
On Wed, Mar 11, 2015 at 4:46 PM, J
On March 12, 2015 06:43:40 AM Gavin Flower wrote:
> Bill cannot comment, but it might be along the lines of assigning all
> intellectual property rights, or something of that ilk. In that case, it
> might give the company ownership of stuff he may have contributed (or
> intends to contribute) to
Hey I hate to bump my post but I would really appreciate some input on this
benchmark. I am very alarmed that adding a very simple partitioning trigger
slows the insert speed by an order of magnitude. Is there any way to speed
this up?
On Mon, Mar 9, 2015 at 11:44 AM, Tim Uckun wrote:
> I wrote
On 03/11/2015 08:52 AM, pinker wrote:
Adrian Klaver-4 wrote
Also per Kevin Grittner and Tom Lane there
is a Nabble issue at work where the list here is not seeing all the
information. Example:
It's because I edited some post. Then is visible only on nabble because
edited version isn't sent bac
Thanks Vincent for your response. I had used the wrong set up program.
Martin
-Original Message-
From: Vincent Veyron [mailto:vv.li...@wanadoo.fr]
Sent: Wednesday, March 11, 2015 12:57 PM
To: Martin Caverly
Cc: 'pgsql-general@postgresql.org'
Subject: Re: [GENERAL] FW: Installation
On Mo
On Mon, 9 Mar 2015 16:35:12 +
Martin Caverly wrote:
> I am trying to install PostgresSQL 9.0.12 (stand-alone, fresh installation),
> but cannot pass the password screen. I have tried these passwords: root,
> Root, Superuser, superuser, postgres, Postgres, Postgressql, postgressql…
> none o
On 12/03/15 01:55, Bill Moran wrote:
On Wed, 11 Mar 2015 13:50:02 +0100
Dorian Hoxha wrote:
I don't see how it could have negative impact on the postgresql project?
It's not like your job will be to find vulnerabilities and not disclose
them ?
I don't think I should discuss the particulars of
On Wed, 11 Mar 2015 08:28:11 -0400
Bill Moran wrote:
>
> I've been asked to sign a legal document related to a PostgreSQL-
> related job opening. I have concerns about the document and that
> signing it could have a negative impact on the PostgreSQL project
> (in addition to personal concerns).
Hi Robert...
On Wed, Mar 11, 2015 at 11:54 AM, Robert Inder
wrote:
> Is our current "frequent pg_dump" approach a sensible way to go about
> things. Or are we missing something? Is there some other way to
> restore one database without affecting the others?
>
As you've been told before, pg
Adrian Klaver-4 wrote
> Also per Kevin Grittner and Tom Lane there
> is a Nabble issue at work where the list here is not seeing all the
> information. Example:
It's because I edited some post. Then is visible only on nabble because
edited version isn't sent back to the mailing list.
Adrian Kl
On Wed, Mar 11, 2015 at 9:55 AM, Andrew Sullivan
wrote:
> On Wed, Mar 11, 2015 at 09:40:09AM -0400, Joseph Kregloh wrote:
> > Have you looked into Barman? http://www.pgbarman.org/ It does what you
> > want. You can take a full daily backup and it keeps track of the WAL
> files
> > to allow for a
On Wed, Mar 11, 2015 at 09:40:09AM -0400, Joseph Kregloh wrote:
> Have you looked into Barman? http://www.pgbarman.org/ It does what you
> want. You can take a full daily backup and it keeps track of the WAL files
> to allow for a PITR.
I just had a look at the documentation (and the rest of your
On Wed, 11 Mar 2015 13:50:02 +0100
Dorian Hoxha wrote:
> I don't see how it could have negative impact on the postgresql project?
> It's not like your job will be to find vulnerabilities and not disclose
> them ?
I don't think I should discuss the particulars of the situation on
the list. That's
I don't see how it could have negative impact on the postgresql project?
It's not like your job will be to find vulnerabilities and not disclose
them ?
On Wed, Mar 11, 2015 at 1:28 PM, Bill Moran
wrote:
>
> I've been asked to sign a legal document related to a PostgreSQL-
> related job opening.
I've been asked to sign a legal document related to a PostgreSQL-
related job opening. I have concerns about the document and that
signing it could have a negative impact on the PostgreSQL project
(in addition to personal concerns).
I'm guessing I'm not the first person to go through this. I'm
ho
On Wed, Mar 11, 2015 at 10:54:56AM +, Robert Inder wrote:
> But, at least while the system is under rapid development, we also
> want to have a way to roll a particular client's database back to a
> (recent) "known good" state, but without affecting any other client.
>
> My understanding is th
We are developing a new software system which is now used by a number
of independent clients for gathering and storing live data as part of
their day to day work.
We have a number of clients sharing a single server. It is running
one Postgres service, and each client is a separate user with acces
Hi,
I am new to postgresql and evaluating the streaming replication for my use
case. My use case is:
1. Need to replicate data from primary database (master) to secondary
database (slave) asynchronously.
2. If master goes down, the slave should automatically be promoted to
master
22 matches
Mail list logo
