pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Floris Van Nee <florisvannee@Optiver.com>
To: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Jesper Pedersen <jesper.pedersen@redhat.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: James Coleman <jtc331@gmail.com>
Cc: Rafia Sabih <rafia.pghackers@gmail.com>
Cc: Jeff Janes <jeff.janes@gmail.com>
Cc: Bhushan Uparkar <bhushan.uparkar@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Alexander Korotkov <a.korotkov@postgrespro.ru>
Subject: RE: Index Skip Scan
Date: Tue, 4 Feb 2020 20:34:09 +0000
Message-ID: <5be025f30d8e45cda167c58b5d5e72d2@opammb0561.comp.optiver.com> (raw)
In-Reply-To: <20200204200205.ip5c2mzy3i2okqey@localhost>
References: <1e59d800b38141c5af2ad3a64cf9758e@opammb0562.comp.optiver.com>
	<802e46fa-dc2c-4c32-e55b-884e04aa7f12@redhat.com>
	<CAH2-Wzk6hvXvZ+1q4JBRunZkxmJwdXxnNsWuKJBp+F+mJuZYZw@mail.gmail.com>
	<20200121160942.eu4bvbu46nt223ug@localhost>
	<a713fef85da14e1fbca51d19c872d023@opammb0562.comp.optiver.com>
	<20200122160441.ograupmzyytde2mi@localhost>
	<1579713885361.64964@Optiver.com>
	<20200122213603.ndlm6t4ryivdwxs7@localhost>
	<20200127103016.ieflsboqveb6iduc@localhost>
	<e198edfa18804c13b6b383b62fbfd94a@opammb0561.comp.optiver.com>
	<20200204200205.ip5c2mzy3i2okqey@localhost>


> this point me and Jesper inclined to go with the second option. But maybe
> I'm missing something, are there any other suggestions?

Unfortunately I figured this would need a more invasive fix. I tend to agree that it'd be better to not skip in situations like this. I think it'd make most sense to make any plan for these 'prepare/fetch' queries would not use skip, but rather a materialize node, right?

-Floris




view thread (248+ messages)  latest in thread

Message-ID: <5be025f30d8e45cda167c58b5d5e72d2@opammb0561.comp.optiver.com>
Permalink:  ../5be025f30d8e45cda167c58b5d5e72d2@opammb0561.comp.optiver.com/
Also on:    postgresql.org/message-id/5be025f30d8e45cda167c58b5d5e72d2@opammb0561.comp.optiver.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: florisvannee@Optiver.com, 9erthalion6@gmail.com, pg@bowt.ie, jesper.pedersen@redhat.com, david.rowley@2ndquadrant.com, tomas.vondra@2ndquadrant.com, horikyota.ntt@gmail.com, alvherre@2ndquadrant.com, thomas.munro@gmail.com, jtc331@gmail.com, rafia.pghackers@gmail.com, jeff.janes@gmail.com, bhushan.uparkar@gmail.com, a.korotkov@postgrespro.ru
  Subject: RE: Index Skip Scan
  In-Reply-To: <5be025f30d8e45cda167c58b5d5e72d2@opammb0561.comp.optiver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox