[GENERAL] Intemittendly get "server process (PID 5884) exited with exit code 3"

Hi, I'm working with postgres version 9.3.10 on Windows. From time to time a postgres process terminates with following messages: LOG: server process (PID 5884) exited with exit code 3 LOG: terminating any other active server processes WARNING: terminating connection because of crash of anoth

Re: [GENERAL] Intemittendly get "server process (PID 5884) exited with exit code 3"

Hi Tom, many thanks for your answer. This is a good hint. Will check this. Regards Jürgen -Ursprüngliche Nachricht- Von: Tom Lane [mailto:t...@sss.pgh.pa.us] Gesendet: Montag, 25. April 2016 17:09 An: Wetzel, Juergen (Juergen) Cc: pgsql-general@postgresql.org Betreff: Re: [GENERAL

[GENERAL] Slow query plan used

I have a question concerning the query planner. I observe that chosen query plan differs on length and content of a like search expression. We have a view combining data from two tables, both containing same number of rows (round about 3). Used PostgreSQL version is 9.3.15 on Windows. DDL of

Re: [GENERAL] Slow query plan used

>> Only 130 rows out of the 3 have ARCHIVED = 0 > in this case i would suggest a partial index: > create index on (archived) where archived = 0; Thanks, Andreas. Sorry for the confusion about the table names. The hint with the partial index sounds as it could solve the problem. I will tes

Re: [GENERAL] Slow query plan used

Am 31.05.2017 um 13:27 schrieb Wetzel, Juergen (Juergen): >>> Only 130 rows out of the 3 have ARCHIVED = 0 >> in this case i would suggest a partial index: >> create index on (archived) where archived = 0; > Thanks, Andreas. > > Sorry for the confusion abo

Re: [GENERAL] Slow query plan used

Andreas Kretschmer writes: > please consider my plan B) and increase the stats. See my other mail. I tried that also. Combined with the partial index. But still same result. Bill Moran writes: > LIKE queries are probably challenging to plan, especially when they're > not > left-anchored: how c