Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-08 Thread Amit Langote
On 2018/10/08 0:09, Michael Paquier wrote: > On Sun, Oct 07, 2018 at 11:13:19AM -0300, Alvaro Herrera wrote: >> Good point. I cannot do that today, but if you want to, please go >> ahead. > > Okay, done. Thank you both. Regards, Amit

Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-07 Thread Michael Paquier
On Sun, Oct 07, 2018 at 11:13:19AM -0300, Alvaro Herrera wrote: > Good point. I cannot do that today, but if you want to, please go > ahead. Okay, done. -- Michael signature.asc Description: PGP signature

Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-07 Thread Alvaro Herrera
On 2018-Oct-07, Michael Paquier wrote: > On Sat, Oct 06, 2018 at 10:15:32PM -0300, Alvaro Herrera wrote: > > Pushed to 11 and master. I'm not convinced that it's a good idea to > > mess with 10 at this point -- the partitioning code is rather completely > > different already ... > > While I defi

Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-07 Thread Michael Paquier
On Sat, Oct 06, 2018 at 10:15:32PM -0300, Alvaro Herrera wrote: > Pushed to 11 and master. I'm not convinced that it's a good idea to > mess with 10 at this point -- the partitioning code is rather completely > different already ... While I definitely agree with you to not mess up with this porti

Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-06 Thread Alvaro Herrera
On 2018-Oct-05, Amit Langote wrote: > On 2018/10/05 16:05, Michael Paquier wrote: > >> As of commit 2fbdf1b38bc [1], which has been applied in 11 and HEAD > >> branches, RelationBuildPartitionDesc emits an error if we don't find > >> relpartbound set for a child found by scanning pg_inherits, inst

Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-05 Thread Michael Paquier
On Fri, Oct 05, 2018 at 04:55:51PM +0900, Amit Langote wrote: > On 2018/10/05 16:05, Michael Paquier wrote: >> Hmm. Indeed, v10 does not complain but HEAD does. (I ran the attached >> SQL file, which is the complete test case both of you have compiled). > > Did you forget to attach some file? Y

Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-05 Thread Amit Langote
On 2018/10/05 16:05, Michael Paquier wrote: >> As of commit 2fbdf1b38bc [1], which has been applied in 11 and HEAD >> branches, RelationBuildPartitionDesc emits an error if we don't find >> relpartbound set for a child found by scanning pg_inherits, instead of >> skipping such children. While that

Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-05 Thread Michael Paquier
On Fri, Oct 05, 2018 at 03:06:52PM +0900, Amit Langote wrote: > To reproduce, the following works too (after creating the objects as > described above): > > alter table partkey_t detach partition partkey_t_1; > alter table partkey_t attach partition partkey_t_1 for values from (0) to > (1000); > E

Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-04 Thread Amit Langote
Thanks for the report. On 2018/10/04 3:58, Rajkumar Raghuwanshi wrote: > Hi, > > I am getting ERROR: null relpartbound for relation 18159 while doing > pg_upgrade from v11 to v11/master. > > -- user-defined operator class in partition key > CREATE FUNCTION my_int4_sort(int4,int4) RETURNS int LA

pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.

2018-10-04 Thread Rajkumar Raghuwanshi
Hi, I am getting ERROR: null relpartbound for relation 18159 while doing pg_upgrade from v11 to v11/master. -- user-defined operator class in partition key CREATE FUNCTION my_int4_sort(int4,int4) RETURNS int LANGUAGE sql AS $$ SELECT CASE WHEN $1 = $2 THEN 0 WHEN $1 > $2 THEN 1 ELSE -1 END; $$