[GENERAL] storage size of "bit" data type..

2007-12-05 Thread Alex Mayrhofer
Hi, i'm trying to find out the storage size for bit(n) data. My initial assumption would be that for any 8 bits, one byte of storage is required. Is this assumption correct? I didn't find that information in the online docs. thanks, Alex ---(end of broadcast)--

[GENERAL] storage size of "bitstring"?

2006-10-22 Thread Alex Mayrhofer
Hi, Two short questions: 1) What storage size does the "bit(n)" data type have? Is it one byte per 8 bits (plus a "length" byte)? I didn't find this in neither the docs nor the list archives ... 2) Additionally, how much storage space does a functional index which returns "boolean" approx. take?

[GENERAL] Order of triggers and sequences...

2006-04-29 Thread Alex Mayrhofer
Hi, i'm about to implement a trigger on a table with an id field populated by a sequence (the usual 'id SERIAL NOT NULL PRIMARY KEY'). Just a short (probably lame) question: Would a "BEFORE INSERT" row level trigger already see a populated 'id' column, or would that happen after all triggers on t

Re: [GENERAL] sound index

2006-04-12 Thread Alex Mayrhofer
Teodor Sigaev wrote: >> also, i'd be happy to listen opinions from people who have experience >> of usage of such things like soundex. I'm using metaphone() together with levenshtein() to search a place name gazetteer database and order the results. That works reasonably well and gives interestin

Re: [GENERAL] index growth

2006-04-09 Thread Alex Mayrhofer
Tom Lane wrote: > Alex Mayrhofer <[EMAIL PROTECTED]> writes: >> i have a bunch of indices over rather frequently updated large tables. Those >> indices grow in size with the updates, so i frequently re-index them. > > That usually shouldn't be necessary since P

[GENERAL] index growth

2006-04-09 Thread Alex Mayrhofer
Hi, i have a bunch of indices over rather frequently updated large tables. Those indices grow in size with the updates, so i frequently re-index them. Are there any plans to add REINDEX estimation/jobs to the autovacuum process - or, alternatively, any options on reducing the growth rate of those

[GENERAL] comparing OLD and NEW in update trigger..

2006-01-26 Thread Alex Mayrhofer
your help on the following two questions: - How can i get the column names of NEW/OLD? Is there a set returning function for this? - Is there a more efficient way to compare whole rows? thanks, Alex Mayrhofer --- http://nona.net/features/map/ ---(end of broadcast)---

[GENERAL] comparing OLD and NEW in update trigger..

2006-01-26 Thread Alex Mayrhofer
;d appreciate your help on the following two questions: - How can i get the column names of NEW/OLD? Is there a set returning function for this? - Is there a more efficient way to compare whole rows? thanks, Alex Mayrhofer --- http://nona.net/features/map/ --

Re: [GENERAL] timestamp <-> ctime conversion question...

2005-12-14 Thread Alex Mayrhofer
Martijn van Oosterhout wrote: On Tue, Dec 13, 2005 at 08:21:20PM +0100, Karsten Hilbert wrote: Presumably this would allow timestamps to be displayed with a timezone other than the current setting. *Display* of timestamptz values at arbitrary time zones is already possible using the "at time zo

[GENERAL] Timestamp <-> ctime conversion question ...

2005-12-13 Thread Alex Mayrhofer
e time zone as well. I'm a bit reluctant to use tricks like manually appending the "Z" as literal text so that it would "look like" a valid UTC time stamp. I'd appreciate any insight on this - am i simply missing something? I'm using PostgreSQL 8.1.0, if tha

[GENERAL] timestamp <-> ctime conversion question...

2005-12-13 Thread Alex Mayrhofer
ses the time zone as well. I'm a bit reluctant to use tricks like manually appending the "Z" as literal text so that it would "look like" a valid UTC time stamp. I'd appreciate any insight on this - am i simply missing something? I'm using PostgreSQL 8.1.0, if tha

Re: [GENERAL] upgrading from backend version 811 to 812

2005-11-08 Thread Alex Mayrhofer
Tom Lane wrote: DETAIL: The database cluster was initialized with PG_CONTROL_VERSION 811, but the server was compiled with PG_CONTROL_VERSION 812. Those are internal version numbers that no one normally ever sees, and certainly no one thinks about. You shouldn't try to outsmart us by referrin

Re: [GENERAL] upgrading from backend version 811 to 812

2005-11-08 Thread Alex Mayrhofer
Jim C. Nasby wrote: 811? 812? We don't have anything close to those version numbers... I'm well aware that PostgreSQL itself is currently at 8.1.0 - however, i'm upgrading from 8.1beta2, and it seems to me that the backend version was modified between those two versions - "811" and "812" seem

[GENERAL] upgrading from backend version 811 to 812

2005-11-08 Thread Alex Mayrhofer
Hi, is there any way to upgrade an 811 backend version cluster to the current 812 version? Any "don't try at home"-type tricks? I'm willing to risk cluster corruption, because this is just a test database (but it is rather large). thanks, alex ---(end of broadca