Date: Tue, 27 Mar 2018 16:00:32 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: Glenn Pierce <glennpierce@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Slow query on partitioned table.
Message-ID: <20180327210032.GW28454@telsasoft.com>
References: 
 <CAM5ipV_iX11SW4EveqauQ=OXcyY5x9_WpM28hWZ-xjyyV=yJbA@mail.gmail.com>
 <20180327144315.GO28454@telsasoft.com>
 <CAM5ipV8Ag6Ft4TBGYs4VGZWAiWoatg91PUw3+3vQehwsLWfOog@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAM5ipV8Ag6Ft4TBGYs4VGZWAiWoatg91PUw3+3vQehwsLWfOog@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

Re-added -performance.

On Tue, Mar 27, 2018 at 05:13:25PM +0100, Glenn Pierce wrote:
> Damn as I was playing with the indexes I must have deleted the constraints :(
> Question if I have a constraint like
> 
> ALTER TABLE sensor_values_2007q1
>   ADD CONSTRAINT sensor_values_2007q1_sensor_id_timestamp_constraint
> UNIQUE (sensor_id, ts);
> 
> will that be used like an index  or do I need to add a separate index ?

Yes:

https://www.postgresql.org/docs/current/static/ddl-constraints.html
|Adding a unique constraint will automatically create a unique B-tree index on
the column or group of columns listed in the constraint

https://www.postgresql.org/docs/current/static/indexes-unique.html
|PostgreSQL automatically creates a unique index when a unique constraint or
|primary key is defined for a table. The index ... is the mechanism that
|enforces the constraint.

Justin