From: | "Pham, Thinh" <tpham(at)mail(dot)priority(dot)net> |
---|---|
To: | pgsql-sql(at)postgreSQL(dot)org |
Subject: | RE: [SQL] Column name's length |
Date: | 1999-06-01 13:25:31 |
Message-ID: | 551413BBBB03D111BF880060B01AACCE0B38EE@home.priority.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Is there any reason you made OIDNAMELEN 260 instead of 256? Also, should i
wait until 6.5 came out before trying to fix this thing? Since it looks like
it's not going to be fixed in 6.5 either. I don't want to dump/reload this
thing too many times since it stores a lot of other more critical data
besides this timeclock thing. I saw the postgres website mentioned that 6.5
is coming out in around one week, is that true?
Thinh
> -----
> diff postgresql-6.4.2/src/include/postgres_ext.h
> postgres-build/src/include/postgres_ext.h
> 34c34
> < #define NAMEDATALEN 32
> ---
> > #define NAMEDATALEN 256
> 37c37
> < #define OIDNAMELEN 36
> ---
> > #define OIDNAMELEN 260
> -----
> diff postgresql-6.4.2/src/include/storage/buf_internals.h
> postgres-build/src/include/storage/buf_internals.h
> 87c87
> < #define PADDED_SBUFDESC_SIZE 128
> ---
> > #define PADDED_SBUFDESC_SIZE 1024
> -----
From | Date | Subject | |
---|---|---|---|
Next Message | Herouth Maoz | 1999-06-01 13:53:17 | Re: [SQL] 'denormalising' with a select |
Previous Message | vineet w.singh | 1999-06-01 08:19:35 | problem in running plpgsql functions |