Re: [GENERAL] size of bytea + performance issues

2006-01-31 Thread Jim C. Nasby
On Tue, Jan 31, 2006 at 08:15:44PM +0100, Jochen Schlosser wrote: > > Well, it's in the FAQ under "How much database disk space is required > > to store data from a typical text file?" but the per tuple overhead is > > between 36 and 44 bytes. depends a bit on the version. > > allright... thx a lo

Re: [GENERAL] size of bytea + performance issues

2006-01-31 Thread Jochen Schlosser
> Well, it's in the FAQ under "How much database disk space is required > to store data from a typical text file?" but the per tuple overhead is > between 36 and 44 bytes. depends a bit on the version. allright... thx a lot! I did not see this point in the FAQ because I am not storing data from a

Re: [GENERAL] size of bytea + performance issues

2006-01-31 Thread Martijn van Oosterhout
On Tue, Jan 31, 2006 at 09:15:18AM -0800, tschak wrote: > Allright... do you mean an alignment with an offset of 4/8 bit or byte? > If it is just bit I cannot really follow the calculation... > Nevertheless it sounds like an explanation for this "effect". > > I have one more question concerning si

Re: [GENERAL] size of bytea + performance issues

2006-01-31 Thread tschak
Allright... do you mean an alignment with an offset of 4/8 bit or byte? If it is just bit I cannot really follow the calculation... Nevertheless it sounds like an explanation for this "effect". I have one more question concerning size. The following table create table test(val0 unsigned smallint,

Re: [GENERAL] size of bytea + performance issues

2006-01-31 Thread Martijn van Oosterhout
On Tue, Jan 31, 2006 at 07:58:30AM -0800, tschak wrote: > Hi everyone, > > my first question concerns the the size of a table with a bytea row. In > the documentation it says something like 4 Bytes + 1 Byte for each > escaped octet sequence per row. For example an insertion into a table > storing