Re: Declarative partitioning - another take

From: Erik Rijkers <er(at)xs4all(dot)nl>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-owner(at)postgresql(dot)org
Subject: Re: Declarative partitioning - another take
Date: 2016-12-07 16:53:28
Message-ID: bf186a19e6b16d104b997e7c1698cb56@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On 2016-12-07 17:38, Robert Haas wrote:
> On Wed, Dec 7, 2016 at 11:34 AM, Amit Langote <amitlangote09(at)gmail(dot)com>
> wrote:
>>> begin;
>>> create schema if not exists s;
>>> create table s.t (c text, d text, id serial) partition by list
>>> ((ascii(substring(coalesce(c, d, ''), 1, 1))));
>>> create table s.t_part_ascii_065 partition of s.t for values in ( 65
>>> );
>>>
>>> it logs as follows:
>>>
>>> 2016-12-07 17:03:45.787 CET 6125 LOG: server process (PID 11503) was
>>> terminated by signal 11: Segmentation fault
>>> 2016-12-07 17:03:45.787 CET 6125 DETAIL: Failed process was running:
>>> create
>>> table s.t_part_ascii_065 partition of s.t for values in ( 65 );
>>
>> Hm, will look into this in a few hours.
>
> My bad. The fix I sent last night for one of the cache flush issues
> wasn't quite right. The attached seems to fix it.

Yes, fixed here too. Thanks.

> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-12-07 17:34:59 Re: patch: function xmltable
Previous Message Robert Haas 2016-12-07 16:38:16 Re: Declarative partitioning - another take