On Sun, Apr 9, 2017 at 11:17 PM, Noah Misch wrote:
> The above-described topic is currently a PostgreSQL 10 open item.
I have committed the patch.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing
On Sat, Mar 25, 2017 at 09:55:21PM +1300, Thomas Munro wrote:
> On Sat, Mar 25, 2017 at 6:04 PM, Amit Kapila wrote:
> > On Tue, Mar 21, 2017 at 5:51 PM, Dilip Kumar wrote:
> >> On Tue, Mar 21, 2017 at 4:47 PM, Thomas Munro
> >>
On Sat, Mar 25, 2017 at 2:25 PM, Thomas Munro
wrote:
>>> I think in this area we need more testing, reason these are not tested
>>> properly because these are not the natural case for parallel bitmap.
>>> I think in next few days I will test more such cases by
On Sat, Mar 25, 2017 at 6:04 PM, Amit Kapila wrote:
> On Tue, Mar 21, 2017 at 5:51 PM, Dilip Kumar wrote:
>> On Tue, Mar 21, 2017 at 4:47 PM, Thomas Munro
>> wrote:
>>> I noticed a failure in the inet.sql test while
On Tue, Mar 21, 2017 at 5:51 PM, Dilip Kumar wrote:
> On Tue, Mar 21, 2017 at 4:47 PM, Thomas Munro
> wrote:
>> I noticed a failure in the inet.sql test while running the regression
>> tests with parallelism cranked up, and can reproduce it
On Wed, Mar 22, 2017 at 5:38 AM, Thomas Munro
wrote:
> Isn't that one row short? What happened to this one?
>
> 10.0.0.0/8 | 10::/8
Actually, In my last test I did not connect to regression database, I
have simply taken table and the few rows from
On Wed, Mar 22, 2017 at 1:21 AM, Dilip Kumar wrote:
> postgres=# SELECT * FROM inet_tbl WHERE i <> '192.168.1.0/24'::cidr
> ORDER BY i;
> c |i
> +--
> 10.0.0.0/8 | 9.1.2.3/8
> 10.0.0.0/8 |
On Tue, Mar 21, 2017 at 4:47 PM, Thomas Munro
wrote:
> I noticed a failure in the inet.sql test while running the regression
> tests with parallelism cranked up, and can reproduce it interactively
> as follows. After an spgist index is created and the plan changes
Hi,
I noticed a failure in the inet.sql test while running the regression
tests with parallelism cranked up, and can reproduce it interactively
as follows. After an spgist index is created and the plan changes to
the one shown below, the query returns no rows.
regression=# set