Re: Bit Varying vs New Column - Mailing list pgsql-novice

From Jean-Yves F. Barbier
Subject Re: Bit Varying vs New Column
Date
Msg-id 20110704214125.4f230e4c@anubis.defcon1
Whole thread Raw
In response to Bit Varying vs New Column  (Barry Laffoon <gotobarry@gmail.com>)
List pgsql-novice
On Mon, 4 Jul 2011 12:26:48 -0700, Barry Laffoon <gotobarry@gmail.com> wrote:



> I have a property on a web form that is multi-select so the property can
> have multiple values. Normally I'd create separate column or a separate row
> for each value. I am thinking of using the BIT VARYING() data type though
> and storing the selected values as a bit mask. So I have several related
> questions:
>
> 1. Any general comments on how this performs?

If you really need speed, consider using BOOLEAN - It is all a matter of
"speed" definition: if you have tons of concurrent requests use BOOLEAN.

--

pgsql-novice by date:

Previous
From: Barry Laffoon
Date:
Subject: Bit Varying vs New Column
Next
From: Vincent Ficet
Date:
Subject: Re: pg_advisory_locks in a multithreaded application context