Re: [GENERAL] Large data and slow queries - Mailing list pgsql-general

From John R Pierce
Subject Re: [GENERAL] Large data and slow queries
Date
Msg-id efdf6a40-6531-1fac-39c5-9d84118ba7e5@hogranch.com
Whole thread Raw
In response to Re: [GENERAL] Large data and slow queries  (vinny <vinny@xs4all.nl>)
Responses Re: [GENERAL] Large data and slow queries  (Samuel Williams <space.ship.traveller@gmail.com>)
Re: [GENERAL] Large data and slow queries  (vinny <vinny@xs4all.nl>)
List pgsql-general
On 4/19/2017 12:31 AM, vinny wrote:
> Given the number of records, my first thought was either partitioning
> or partial-indexes.
> The fewer rows are in the index, the quicker it will be to check,
> and it's not a lot of work to create separate indexes for lat/long
> ranges or dates.

that only works if the planner can figure out which partitions to use in
advance, otherwise it ends up having to scan all the partitions.


--
john r pierce, recycling bits in santa cruz



pgsql-general by date:

Previous
From: Tom DalPozzo
Date:
Subject: Re: [GENERAL] tuple statistics update
Next
From: Moreno Andreo
Date:
Subject: Re: [GENERAL] # of connections and architecture design