‐‐‐ Original Message ‐‐‐
On Wednesday, June 26, 2019 4:07 PM, Tomas Vondra
wrote:
> That might be dangerous, if there may be differences in contents of
> catalogs. I don't think the patch does that though, and for me it works
> just fine. I can initdb database using current master, cre
On Wed, Jun 26, 2019 at 02:12:55PM +, pguser wrote:
‐‐‐ Original Message ‐‐‐
On Wednesday, June 26, 2019 2:55 PM, pguser wrote:
‐‐‐ Original Message ‐‐‐
On Wednesday, June 26, 2019 1:07 PM, Dmitry Dolgov 9erthali...@gmail.com wrote:
> > On Wed, Jun 26, 2019 at 1:53 PM pgu
‐‐‐ Original Message ‐‐‐
On Wednesday, June 26, 2019 2:55 PM, pguser wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, June 26, 2019 1:07 PM, Dmitry Dolgov 9erthali...@gmail.com
> wrote:
>
> > > On Wed, Jun 26, 2019 at 1:53 PM pguser pgu...@diorite.uk wrote:
> > > If I apply th
‐‐‐ Original Message ‐‐‐
On Wednesday, June 26, 2019 1:07 PM, Dmitry Dolgov <9erthali...@gmail.com>
wrote:
> > On Wed, Jun 26, 2019 at 1:53 PM pguser pgu...@diorite.uk wrote:
> > If I apply the latest patch (which says 1 of 2? - maybe I'm missing a part
> > of the patch?), I apply with
> On Wed, Jun 26, 2019 at 1:53 PM pguser wrote:
>
> If I apply the latest patch (which says 1 of 2? - maybe I'm missing a part of
> the patch?), I apply with
Hi,
First of all, thanks for evaluation!
> psql (12beta2)
> Type "help" for help.
>
> db1=> show enable_indexskipscan;
> enable_indexski
Hello
This is my first posting to hackers so sorry if I'm taking up valuable time.
I'm currently migrating a packaged application which supported oracle and sql
server to PostgreSQL.
Something that I've identified as hurting the performance a lot is loose index
scanning. I don't have access to
