Hello again Jeff,
Below is the script that creates one partition table:
CREATE TABLE public.precio_20170301 PARTITION OF public.precio
(
CONSTRAINT precio_20170301_pkey PRIMARY KEY (fecha, pluid, loccd),
CONSTRAINT precio_20170301_almacen_fk FOREIGN KEY (loccd)
REFERENCES public.almacen (loccd) MATCH SIMPLE
ON UPDATE NO ACTION
ON DELETE NO ACTION,
CONSTRAINT precio_20170301_producto_fk FOREIGN KEY (pluid)
REFERENCES public.producto (pluid) MATCH SIMPLE
ON UPDATE NO ACTION
ON DELETE NO ACTION
)
FOR VALUES FROM ('2017-03-01') TO ('2017-03-02')
TABLESPACE pg_default;
I reproduce same test in a empty partition and got same result (15s) at planning
time when I used the virtual table (PRECIO), and an instantly EXPLAIN when I used
the partition directly.
Regards,
Sanyo Capobiango
Em ter, 27 de nov de 2018 às 17:35, Jeff Janes <jeff.janes@xxxxxxxxx> escreveu:
On Tue, Nov 27, 2018 at 9:17 AM Sanyo Moura <sanyo.moura@xxxxxxxxx> wrote:Hi,I'm running performance tests for my application at version 11.1 and encounteredqueries with high planning time compared to the same planning, running at versions 10.5 and 11.0.Can you reproduce the regression if the tables are empty? If so, can you share the create script that creates the tables?Cheers,Jeff
