In article <[EMAIL PROTECTED]>,
> PFC wrote:
>
> > So, where to go from that ? I don't see a way to implement this without
> > a (backwards-compatible) change to the wire protocol, because the clients
> > will want to specify when a plan should be cached or not. Since the user
> > should
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Jim Nasby) wrote:
> Two more ideas for the manager, now that we seem to have consensus to
> build one.
>
One other thing a webapp would allow that would help grow the community.
If the patches are all in a public place then reviewer wannabe
I don't know if this has come up yet but
In terms of tagging errors we might be able to use some machine
learning techniques.
There are NLP/learning systems that interpret logs. They learn over
time what is normal and what isn't and can flag things that are
abnormal.
For example,
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Andrew Sullivan) wrote:
> On Thu, Oct 12, 2006 at 08:34:45AM +0200, Florian Weimer wrote:
> >
> > Some statistics are very hard to gather from a sample, e.g. the number
> > of distinct values in a column.
>
> I like the suggestion, though, tha
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Jim Nasby) wrote:
> I'd love to have the ability to control toasting thresholds
> manually. ... Being able to force a field to be
> toasted before it normally would could drastically improve tuple
> density without requiring the developer t
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] ("Jim C. Nasby") wrote:
> On Wed, Aug 09, 2006 at 08:31:42AM -0400, Perez wrote:
> > Every once in a while people talk about collecting better statistics,
> > correlating multi-column correlations etc. But there
In article <[EMAIL PROTECTED]>,
Perez <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] (Tom Lane) wrote:
>
> > Martijn van Oosterhout writes:
> > > My main problem is that selectivity is the wrong measurement.
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Tom Lane) wrote:
> Martijn van Oosterhout writes:
> > My main problem is that selectivity is the wrong measurement. What
> > users really want to be able to communicate is:
>
> > 1. If you join tables a and b on x, the number of resulting rows
