| From: | Einar Indridason <einari(at)f-prot(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: FAQ (disk space) |
| Date: | 2004-01-26 10:48:55 |
| Message-ID: | 20040126104855.GB31868@f-prot.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jan 24, 2004 at 09:29:12PM -0500, Bruce Momjian wrote:
> Clarence Gardner wrote:
> > >> Could you please tell me if there's a limit in the amount of records that
> > >> the database can handle?
> >
> > >See the FAQ: http://www.postgresql.org/docs/faqs/FAQ.html#4.5
> >
> > Speaking of the FAQ, in the next question (#4.6), should
> > "NULLs are stored in bitmaps" say "NULL indicators are stored in bitmaps"?
>
> I changed it to:
>
> NULLs are stored _as_ bitmaps
Eh... good morning folks. I have been lurking on the postgreSQL lists
for a while. Now when I read this, a question arise.
Does postgres calculate some sort of a "checksum" over a row?
I mean... storing whether a field is NULL or not inside a single bit,
seems slightly risky (especially when we consider how much of the
hardware out there, is of marginal quality).
Would it be worth it to calculate some sort of a checksum over a row, and
store that checksum along with the row?
Cheers,
--
Einar Indridason
einari(at)f-prot(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tabai | 2004-01-26 10:56:30 | About Privileges |
| Previous Message | Fred Moyer | 2004-01-26 08:26:00 | Re: Object Relational features in PostgreSQL |