Re: Problem in Parallel Bitmap Heap Scan?

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem in Parallel Bitmap Heap Scan?
Date: 2017-03-22 00:08:44
Message-ID: CAEepm=0My3PPh6tNSOkkikq0WTc4Fex1mxqbK=Jj05mL0ZLFXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 22, 2017 at 1:21 AM, Dilip Kumar <dilipbalaut(at)gmail(dot)com> 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 | 10.1.2.3/8
> 10.0.0.0/32 | 10.1.2.3/8
> 10.0.0.0/8 | 10.1.2.3/8
> 10.1.0.0/16 | 10.1.2.3/16
> 10.1.2.0/24 | 10.1.2.3/24
> 10.1.2.3/32 | 10.1.2.3
> 10.0.0.0/8 | 11.1.2.3/8
> 192.168.1.0/24 | 192.168.1.226/24
> 192.168.1.0/24 | 192.168.1.255/24
> 192.168.1.0/24 | 192.168.1.0/25
> 192.168.1.0/24 | 192.168.1.255/25
> 192.168.1.0/26 | 192.168.1.226
> ::ffff:1.2.3.4/128 | ::4.3.2.1/24
> 10:23::f1/128 | 10:23::f1/64
> 10:23::8000/113 | 10:23::ffff
> (16 rows)

Isn't that one row short? What happened to this one?

10.0.0.0/8 | 10::/8

--
Thomas Munro
http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-03-22 00:10:24 Re: increasing the default WAL segment size
Previous Message Michael Paquier 2017-03-21 23:47:26 Re: Automatic cleanup of oldest WAL segments with pg_receivexlog