Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

On Sat, Jan 7, 2017 at 2:56 AM, Job wrote: > Hi guys, > > really much appreciated your replies. > > >> You might want to include the query plans for each server > > W e use a function, the explain analyze is quite similar: > POSTGRESQL 8.4.22: > > explain analyze

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

On Fri, Jan 6, 2017 at 4:56 PM, Alban Hertroys wrote: > > > On 6 Jan 2017, at 16:56, Job wrote: > > > > W e use a function, the explain analyze is quite similar: > > POSTGRESQL 8.4.22: > > Total runtime: 1.531 ms > > > > POSTGRES 9.6.1: > >

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

> On 6 Jan 2017, at 16:56, Job wrote: > > W e use a function, the explain analyze is quite similar: > POSTGRESQL 8.4.22: > Total runtime: 1.531 ms > > POSTGRES 9.6.1: > Execution time: 4.230 ms Are you being serious? You're complaining about a "big slowdown" for

Re: [GENERAL] Queries on very big table

On Mon, Jan 2, 2017 at 5:23 AM, Job wrote: > Hello guys and very good new year to everybody! > > We are now approaching some queries and statistics on very big table (about > 180 millions of record). > The table is partitioned by day (about ~3 Gb of data for every

Re: [GENERAL] [BUGS] Postgresql query HAVING do not work

Looking at tutorial I can not replicate those querys to Postgresql without serious editing. But, I simply want to create a hierarchical model tree that look like Amazon. What's your general solution on that can work better and easy to maintain than Nested Set Model with update lock? On 1/5/17

Re: [GENERAL] Queries on very big table

Hi, It is better to use a data warehouse software with columnar storage(clickhouse, greenplum etc) for BI queries on large datasets but data offloading could be a complicated task. It is possible to try tune postgres and the environment it works in to process query such as yours faster. You

Re: [GENERAL] PostgreSQL not reusing free space in table ?

On Friday, January 6, 2017 9:00:06 AM CET Merlin Moncure wrote: > On Fri, Jan 6, 2017 at 4:09 AM, Pierre Ducroquet > > wrote: > > Hi > > > > Running PostgreSQL 9.4, I am running in the following issue. > > On a huge table, I have to remove the content (set to

R: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

Hi guys, really much appreciated your replies. >> You might want to include the query plans for each server W e use a function, the explain analyze is quite similar: POSTGRESQL 8.4.22: explain analyze select 'record.com' where 'record.com' like '%.%' and function_cloud_view_orari('53',

Re: [GENERAL] Write-optimized data structures

On Thu, Dec 29, 2016 at 4:03 PM, selforganized wrote: > Hi, > > Does Postgresql have any write-optimized data structure like LSM-tree? if > not is there any plan to implement that? > > I'm building a write-heavy OLTP application. I'm looking at write-optimized > databases

Re: [GENERAL] PostgreSQL not reusing free space in table ?

On Fri, Jan 6, 2017 at 4:09 AM, Pierre Ducroquet wrote: > Hi > > Running PostgreSQL 9.4, I am running in the following issue. > On a huge table, I have to remove the content (set to '') of a column that > makes for 99% of the weight of the table. Since the

Re: [GENERAL] psql error (encoding related?)

On 01/06/2017 05:32 AM, BRUSSER Michael wrote: Thank you Torsten and Tom, this rang the bell and put me on the right track. " This should be a can't-happen failure ..." - indeed, the wound is self-inflicted. Can you share what the cause was as history has shown that if one person makes a

Re: [GENERAL] requested timeline doesn't contain minimum recovery point

2017-01-06 13:09 GMT+01:00 Michael Paquier : > On Fri, Jan 6, 2017 at 1:01 AM, Tom DalPozzo wrote: > > Hi, > > there is something happening in my replication that is not clear to me. I > > think I'm missing something. > > I've two server, red and

Re: [GENERAL] psql error (encoding related?)

Thank you Torsten and Tom, this rang the bell and put me on the right track. >> " This should be a can't-happen failure ..." - indeed, the wound is >> self-inflicted. Michael. -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Thursday, January 05, 2017 5:04 PM To:

Re: [GENERAL] requested timeline doesn't contain minimum recovery point

On Fri, Jan 6, 2017 at 1:01 AM, Tom DalPozzo wrote: > Hi, > there is something happening in my replication that is not clear to me. I > think I'm missing something. > I've two server, red and blue. > red is primary blue is standby, async repl. > Now: > 1 cleanly stop red > 2

[GENERAL] PostgreSQL not reusing free space in table ?

Hi Running PostgreSQL 9.4, I am running in the following issue. On a huge table, I have to remove the content (set to '') of a column that makes for 99% of the weight of the table. Since the production can not be stopped, I will not be able to do a VACUUM FULL nor any direct rewrite of the