"Fred Ingham" <[EMAIL PROTECTED]> writes:
> After dropping and recreating the indexes I have (in KB):
Ah, that's more like it.
> So, it appears that I am running into the pathological case.
Actually, a simpler explanation would be if you'd done a bunch of
updates and/or deletes at some point.
Tom,
Again, thank you for your quick and knowledgeable assistance.
After dropping and recreating the indexes I have (in KB):
oldnew
PostgreSQL pinndex_seq 8 8
pinndx 7,856 7,856
pinndx_pkey 6,984 6,984 (did not recreate)
"Fred Ingham" <[EMAIL PROTECTED]> writes:
> PostgreSQL pinndex_seq 8
> pinndx 7,856
> pinndx_pkey 6,984
> parent_ndx 6,952
> tagpath_ndx 5,552
> tagname_ndx 5,560
> atrname_ndx 5,696
> pinnum_ndx
nding on the number
of
> set members (64 members maximum)
>
> Fred
>
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 27, 2001 1:48 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] PostgreSQL and mySQ
ing on the number of
> set members (64 members maximum)
>
> Fred
>
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 27, 2001 1:48 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] PostgreSQL
Did you see the FAQ items on estimating database sizes? Does MySQL have
less overhead per row?
[ Charset ISO-8859-1 unsupported, converting... ]
> To all,
>
> Before I begin, this is NOT a PostgreSQL verses mySQL post. I have used
> both databases and have found both of these products to be ex
TECTED]]
Sent: Friday, April 27, 2001 1:48 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] PostgreSQL and mySQL database size question
Did you see the FAQ items on estimating database sizes? Does MySQL have
less overhead per row?
---(end o
