On Wed, 27 Sep 2017 11:31:54 +0200
Tomas Vondra wrote:
> On 09/27/2017 10:08 AM, Jonathan Moules wrote:
> > Hi,
> > (Postgres 9.5 and 9.6)
> > We have a table of about 650million rows. It's a partitioned table, with
> > two "child" tables. We want to change its primary key type from int to
> > bi
On Sat, 16 Sep 2017 12:15:46 +0200
Rafal Pietrak wrote:
> W dniu 16.09.2017 o 09:33, Jehan-Guillaume de Rorthais pisze:
> >
> [-]
> >
> > I wrote something about this some years ago, this might do the trick for
> > you, maybe with some adjustments depending on your schema. The mai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 01/11/2010 20:54, hubert depesz lubaczewski a écrit :
> On Mon, Nov 01, 2010 at 08:31:10PM +0100, Cédric Villemain wrote:
>> It should stick at a maximum of 3 * checkpoint_segments + 1, if it
>> exceed it will remove the extra files after.
>
> if y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/2010 16:00, Tom Lane wrote:
> "Jehan-Guillaume (ioguix) de Rorthais" writes:
>> Shouldn't locks only be on tables/indexes that are actually used by the
>> planner ?
>
> Well, yeah, they are. The planne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have some trouble understanding the locking policy with partitioned
tables. Here is a simple schema based on a real one:
CREATE DATABASE test;
\c test
CREATE TABLE test(
id integer PRIMARY KEY,
id_dummy integer,
id_part1 integer
