Re: [GENERAL] Need advice for handling big data in postgres

2015-01-15 Thread Jim Nasby
On 1/15/15 7:42 AM, Vincent Veyron wrote: On Wed, 14 Jan 2015 11:42:45 +1100 Tobias Fielitz wrote: OPTION 1 - PARTITIONING: For each query only a few columns are interesting and I could partition the table (as it was suggested on SO) by *created* and by *code*. There is roughly 10 different co

Re: [GENERAL] Need advice for handling big data in postgres

2015-01-15 Thread Vincent Veyron
On Wed, 14 Jan 2015 11:42:45 +1100 Tobias Fielitz wrote: > > OPTION 1 - PARTITIONING: > For each query only a few columns are interesting and I could partition > the table (as it was suggested on SO) > by *created* and by *code*. > There is roughly 10 different codes and I would keep data for the

[GENERAL] Need advice for handling big data in postgres

2015-01-13 Thread Tobias Fielitz
Hi, I am quite new to handle a lot of data in Postgres and I would be happy to get as much advice from experienced data jongleurs as possible. THE SCENARIO: I have a big table `client_log`. It is the "main gate" for clients (and there is a lot of them) to talk to the backend. Each client sends mo