On Thu, 28 Jul 2016 at 01:18 Gavin Flower
wrote:
> On 28/07/16 17:52, Jason Dusek wrote:
> > With regards to write amplification, it makes me think about about
> > OIDs. Used to be, every row had an OID and that OID persisted across
> > row versions.
> >
> >
> https://www.postgresql.org/docs/9.5/
On 07/30/2016 10:52 AM, Edson Richter wrote:
Dear community,
Sorry if this is not the right place for proposing new features. Also,
sorry if I'm proposing something already existing.
I do currently use the "debug" extension to better understand the
entrophy of my application regarding database
* David Steele (da...@pgmasters.net) wrote:
> On 7/29/16 5:31 PM, Rakesh Kumar wrote:
> > Sure.
> >
> > 1 - You ran pg_basebackup on node-1 against a live cluster and store
> > it on NFS or tape.
> > 2 - Do a restore on node-2 from the backup taken on (1), but only for
> > a subset of the databas
Dear community,
Sorry if this is not the right place for proposing new features. Also,
sorry if I'm proposing something already existing.
I do currently use the "debug" extension to better understand the
entrophy of my application regarding database.
But in production this is not possible,
Hi all, I seem to be in a bit of a jam with the query planner choosing
a significantly less optimal route for a query.
First, a common check list I've seen around when researching these
types of issues on list:
1. pgsql version is PostgreSQL 9.4.7 running on Amazon RDS
2. Vacuum analyze was run
3
