Tom Lane wrote:
I'll run some benchmarks tomorrow, as it's rather late in my time zone.
If anyone wants to post some benchmark results, they are welcome to.
> I disagree completely with the idea of forcing this behavior for all
> datatypes. It could only be sensible for fairly wide values; you don't
> save enough to justify the lossiness otherwise.
I think it would be premature to decide about this before we see some
performance numbers. I'm not fundamentally opposed, though.
> [ BTW, posting patches to pgsql-general seems pretty off-topic. ]
Not any more than discussing implementation details is :) But your point
is well taken, I'll send future patches to -patches.
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2005-05-11 14:18:34|
|Subject: Re: Optimizer wrongly picks Nested Loop Left Join |
|Previous:||From: John A Meinel||Date: 2005-05-11 14:04:47|
|Subject: Re: Optimizer wrongly picks Nested Loop Left Join|
pgsql-general by date
|Next:||From: Mark Borins||Date: 2005-05-11 14:47:21|
|Subject: Disabling Triggers|
|Previous:||From: Csaba Nagy||Date: 2005-05-11 14:01:17|
|Subject: Re: Fixing a too long column value in a before insert|