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
> And, to give you a starting point: the discussion has morphed into:
> "What manual ways can we come up with for the DBA to
> influence the planner and fix planner "bugs" which won't have
> the fragility of query-based hints ala Oracle?"
I see a few downsides though:
1. it lacks a way to try
Martijn van Oosterhout writes:
> Which could then be used by the planner. Or more directly:
>
> CREATE HISTOGRAM FOR FUNCTION verify_pk_signature(documenent)
> AS ( true = 99, false = 1 );
>
> (Perhaps DECLARE is the better phrase?).
Except that the distribution is a property of the values y
Mark,
That is sort of the stopping block. None of us "know" what it should look
like, but leaving the topic as "if you want it, go do the work and submit
a patch." Isn't going to get it done.
First we should decide if it is, in fact, something that ought to happen,
then if that happens, we shou
On Thu, Oct 12, 2006 at 02:25:29PM +0100, Simon Riggs wrote:
> The CREATE OPERATOR command already has a RESTRICT=res_proc clause which
> provides the ability to attach selectivity functions onto an operator.
>
> So this is already possible if you turn radius_authenticate() into an
> operator. The
On Thu, 2006-10-12 at 15:06 +0200, Martijn van Oosterhout wrote:
> On Thu, Oct 12, 2006 at 08:50:04AM -0400, Greg Stark wrote:
> > Not to say this isn't a good idea -- i think it's a great idea. But note
> > that
> > it doesn't solve some of the use cases of hints. Consider something like:
> >
>
Mark Woodward wrote:
>
> Exactly. IMHO, it is a frustrating environment. PostgreSQL is a great
> system, and while I completely respect the individuals involved, I think
> the "management" for lack of a better term, is difficult.
'course you're welcome to fork the project as well if your style
an
On Thu, Oct 12, 2006 at 08:50:04AM -0400, Greg Stark wrote:
> Not to say this isn't a good idea -- i think it's a great idea. But note that
> it doesn't solve some of the use cases of hints. Consider something like:
>
> WHERE NOT radius_authenticate(suspected_hacker)
>
> or
>
> WHERE NOT ver
Simon Riggs <[EMAIL PROTECTED]> writes:
> The *right* place, IMHO, for planner information is to decorate the
> tables, columns and relationships so that *every* SQL statement can pick
> that up. If the world changes, you make one change and all your SQL
> benefits. As the analyzers improve, you
> Clinging to sanity, [EMAIL PROTECTED] ("Mark Woodward") mumbled into
> her beard:
>> What is the point of writing a proposal if there is a threat of
>> "will be rejected" if one of the people who would do the rejection
>> doesn't at least outline what would be acceptable?
>
> If your proposal is
On Wed, 2006-10-11 at 19:18 -0400, Mark Woodward wrote:
> >
> > Since you're the one who wants hints, that's kind of up to you to define.
> > Write a specification and make a proposal.
> >
>
> What is the point of writing a proposal if there is a threat of "will be
> rejected" if one of the people
"Mark Woodward" <[EMAIL PROTECTED]> writes:
> What is the point of writing a proposal if there is a threat of "will be
> rejected" if one of the people who would do the rejection doesn't at least
> outline what would be acceptable?
FWIW, I said some things about what I'd consider a good design in
Clinging to sanity, [EMAIL PROTECTED] ("Mark Woodward") mumbled into her beard:
>> Mark,
>>
>> First off, I'm going to request that you (and other people) stop
>> hijacking Simon's thread on hypothetical indexes. Hijacking
>> threads is an effective way to get your ideas rejected out of hand,
>> j
Mark Woodward wrote:
Since you're the one who wants hints, that's kind of up to you to
define.
Write a specification and make a proposal.
>>> What is the point of writing a proposal if there is a threat of "will be
>>> rejected" if one of the people who would do the rejection do
>>>
>>> Since you're the one who wants hints, that's kind of up to you to
>>> define.
>>> Write a specification and make a proposal.
>>>
>>
>> What is the point of writing a proposal if there is a threat of "will be
>> rejected" if one of the people who would do the rejection doesn't at
>> least
>>
>>
>> Since you're the one who wants hints, that's kind of up to you to define.
>> Write a specification and make a proposal.
>>
>
> What is the point of writing a proposal if there is a threat of "will be
> rejected" if one of the people who would do the rejection doesn't at least
> outline what
> Mark,
>
> First off, I'm going to request that you (and other people) stop hijacking
> Simon's thread on hypothetical indexes. Hijacking threads is an
> effective way to get your ideas rejected out of hand, just because the
> people whose thread you hijacked are angry with you.
>
> So please ob
Mark,
First off, I'm going to request that you (and other people) stop hijacking
Simon's thread on hypothetical indexes. Hijacking threads is an
effective way to get your ideas rejected out of hand, just because the
people whose thread you hijacked are angry with you.
So please observe the
18 matches
Mail list logo
