Re: [PERFORM] vacuum analyze affecting query performance

Thanks for the info! -- View this message in context: http://www.postgresql-archive.org/vacuum-analyze-affecting-query-performance-tp5970681p5970830.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com. -- Sent via pgsql-performance mailing list (pgsql-performance@p

[PERFORM] vacuum analyze affecting query performance

We are on Postgres 9.5, and have been running a daily vacuum analyze on the entire database since 8.2 The data has grown exponentially since, and we are seeing that queries are now being significantly affected while the vacuum analyze runs. The query database is a Slony slave. So the question is,

Re: -EXT-[PERFORM] Re: Table not using tsvector gin index and performance much worse than when it uses it.

Yup, I just found the per index option. Pretty cool. Will see what value is optimal... Thanks RV -- View this message in context: http://www.postgresql-archive.org/Table-not-using-tsvector-gin-index-and-performance-much-worse-than-when-it-uses-it-tp5954485p5954521.html Sent from the PostgreSQL

Re: -EXT-[PERFORM] Re: Table not using tsvector gin index and performance much worse than when it uses it.

Ok, appreciate the feedback. Will play around with those settings as well. Maybe start with default which is 50 I believe. Thanks! RV -- View this message in context: http://www.postgresql-archive.org/Table-not-using-tsvector-gin-index-and-performance-much-worse-than-when-it-uses-it-tp5954485p

[PERFORM] Re: Table not using tsvector gin index and performance much worse than when it uses it.

Thanks for the response! * We are on version 9.5.6 * Less than 10% of the table was updated today (between the time of the last reindex to when performance deteriorated) * autovacuum is on. I don't see an autoanalyze property in config but these are the settings for analyze /autovacuum_analyze_

[PERFORM] Table not using tsvector gin index and performance much worse than when it uses it.

Hi, I have a table with 22k rows - not large at all. I have a couple of indices on it as well as a gin index on a tsvector column. If I reindex the table and run a query it takes ~20ms to execute using the tsvector-gin index. By the end of the day, the planner decides not to use the gin index and

Re: [PERFORM] Postgres partitions-query scanning all child tables

AM, rverghese <[hidden email]> wrote: Ok, thanks. Thats a bummer though. That means I need a table for every month/year combination. I was hoping to limit it to 12 tables. Riya If you wanted to have a column called month_num or something like that, and if *all* of your queries extra

Re: [PERFORM] Postgres partitions-query scanning all child tables

all child tables On Wed, Jan 27, 2016 at 5:09 PM, rverghese <[hidden email]> wrote: Hi I have a master table and the inherited tables broken up by month. /e.g. CONSTRAINT transactions_january_log_date_check CHECK (date_part('month'::text, log_date) = 1::double pre

[PERFORM] Postgres partitions-query scanning all child tables

Hi I have a master table and the inherited tables broken up by month. /e.g. CONSTRAINT transactions_january_log_date_check CHECK (date_part('month'::text, log_date) = 1::double precision);/ So transactions_master is the master table, and then transactions_january, transactions_february, etc. I h