Re: [GENERAL] Table Design for Many Updates

2017-01-10 Thread Craig Boucher
, Craig From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce Sent: Tuesday, January 10, 2017 1:48 PM To: pgsql-general@postgresql.org Subject: Re: [GENERAL] Table Design for Many Updates On 1/10/2017 1:42 PM, David G. Johnston wrote

Re: [GENERAL] Table Design for Many Updates

2017-01-10 Thread Craig Boucher
: Re: [GENERAL] Table Design for Many Updates On Tue, Jan 10, 2017 at 2:33 PM, Craig Boucher mailto:cr...@wesvic.com> > wrote: I have a multi-tenant database that I'm migrating from SQL Server to PostgreSQL 9.6.1. I read the recent articles about the potential write amplificatio

Re: [GENERAL] Table Design for Many Updates

2017-01-10 Thread John R Pierce
On 1/10/2017 1:42 PM, David G. Johnston wrote: On Tue, Jan 10, 2017 at 2:33 PM, Craig Boucher >wrote: I have a multi-tenant database that I'm migrating from SQL Server to PostgreSQL 9.6.1. I read the recent articles about the potential write amplification is

Re: [GENERAL] Table Design for Many Updates

2017-01-10 Thread David G. Johnston
On Tue, Jan 10, 2017 at 2:33 PM, Craig Boucher wrote: > I have a multi-tenant database that I'm migrating from SQL Server to > PostgreSQL 9.6.1. I read the recent articles about the potential write > amplification issue in Postgres. I have one particular table that has 14 > columns, a primary k

[GENERAL] Table Design for Many Updates

2017-01-10 Thread Craig Boucher
I have a multi-tenant database that I'm migrating from SQL Server to PostgreSQL 9.6.1. I read the recent articles about the potential write amplification issue in Postgres. I have one particular table that has 14 columns, a primary key, five foreign keys, and eight indexes. We have a little over