Skip site navigation (1) Skip section navigation (2)

Re: "Truncated" tuples for tuple hash tables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "Truncated" tuples for tuple hash tables
Date: 2006-06-26 21:08:27
Message-ID: 23001.1151356107@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Mon, 2006-06-26 at 16:43 -0400, Tom Lane wrote:
>> analyze.c (tuples collected in-memory for stats analysis)

> Do we save enough there for us to care?

Possibly not --- it's certainly low-priority, but I listed it for
completeness.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-06-26 21:26:03
Subject: Re: [HACKERS] Overhead for stats_command_string et al, take 2
Previous:From: Greg StarkDate: 2006-06-26 21:03:54
Subject: Re: Inheritance, CREATE TABLE LIKE, and partitioned tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group