Re: [GENERAL] Performance implications of adding a "disabled" column to a table

2012-08-30 Thread Seref Arikan
st 30, 2012 12:48 PM > To: PG-General Mailing List > Subject: [GENERAL] Performance implications of adding a "disabled" column > to > a table > > Greetings, > I have a large number of rows (up to 3-4 millions) that I'll either be > fetching into ram (if it is a

Re: [GENERAL] Performance implications of adding a "disabled" column to a table

2012-08-30 Thread David Johnston
From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Seref Arikan Sent: Thursday, August 30, 2012 12:48 PM To: PG-General Mailing List Subject: [GENERAL] Performance implications of adding a "disabled" column to a table Greetings, I ha

[GENERAL] Performance implications of adding a "disabled" column to a table

2012-08-30 Thread Seref Arikan
Greetings, I have a large number of rows (up to 3-4 millions) that I'll either be fetching into ram (if it is a few thousand rows), or scrolling through a cursor. Deletions or updates on content of these rows lead to expensive operations in my business logic, so I simply need to mark them as disabl