Re: [PATCHES] hashlittle(), hashbig(), hashword() and endianness

2007-11-16 Thread Alex Vinokur
On Nov 15, 1:23 pm, [EMAIL PROTECTED] (Heikki Linnakangas) wrote: > Alex Vinokurwrote: > > On Nov 15, 10:40 am,Alex Vinokur<[EMAIL PROTECTED]> > > wrote: > > [snip] > >> I have some question concerning Bob Jenkins' functions > >> hashword(uint32_t*, size_t), hashlittle(uint8_t*, size_t) and > >> ha

[PATCHES] Problem with pg_dump -n schemaname

2007-11-16 Thread Zoltan Boszormenyi
Hi, we came across a problem when you want to dump only one schema. The ASCII output when loaded with psql into an empty database doesn't produce an identical schema to the original. The problem comes from this statement ordering: SET ... -- some initial DB parameters ... SET search_path = schem

Re: [PATCHES] hashlittle(), hashbig(), hashword() and endianness

2007-11-16 Thread Kenneth Marshall
On Fri, Nov 16, 2007 at 01:19:13AM -0800, Alex Vinokur wrote: > On Nov 15, 1:23 pm, [EMAIL PROTECTED] (Heikki Linnakangas) > wrote: > > Alex Vinokurwrote: > > > On Nov 15, 10:40 am,Alex Vinokur<[EMAIL PROTECTED]> > > > wrote: > > > [snip] > > >> I have some question concerning Bob Jenkins' function

[PATCHES] Proposed patch for ANALYZE overcounting dead rows

2007-11-16 Thread Tom Lane
There's been a thread in pgsql-performance about ANALYZE reporting an overly large number of dead rows because it counts anything that's not visible-per-SnapshotNow-rules as "dead", in particular insert-in-progress tuples are reported as "dead". This seems a bad idea because it may prompt autovacu