OK, tricky, but fixed --- patch attached and applied, with documentation
updates. Here is the test query:
test=> select (CURRENT_DATE + '05:00'::time)::timestamp at time zone
'Canada/Pacific';
timezone
2005-07-22 08:00:00-
On Thu, Jul 21, 2005 at 09:19:04PM -0700, Luke Lonergan wrote:
> Joshua,
>
> On 7/21/05 7:53 PM, "Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
> > Well I know that isn't true at least not with ANY of the Dells my
> > customers have purchased in the last 18 months. They are still really,
> > really
This patch fixes the interval regression on my AIX box (kookaburra) by
only doing integer math on the interval, instead of float/double math.
I think this is the correct way to handle this, since it's an integer
data type.
I don't know if it will fix Olivier's problem, since I wasn't able to
repr
On Fri, 2005-07-22 at 09:40 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > In general, the hint bits are good. In *some* cases, not. I still seek
> > control over that as a designer.
...
> ... not be worth
> solving with a knob as klugy and potentially dangerous as
> suppres
Luke Lonergan wrote:
Joshua,
On 7/21/05 7:53 PM, "Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
Well I know that isn't true at least not with ANY of the Dells my
customers have purchased in the last 18 months. They are still really,
really slow.
That's too bad, can you cite some model numbers
Simon Riggs <[EMAIL PROTECTED]> writes:
> In general, the hint bits are good. In *some* cases, not. I still seek
> control over that as a designer.
> Specifically, the scenario I want to optimize is this:
> - we load a table with lots of real time measurement data, as one child
> out of a large nu
On Wed, 2005-07-20 at 13:20 -0400, Tom Lane wrote:
> > When VACUUM freezes the xid, it *does* make sense at that point to
> > update the hint bits as a performance optimization.
>
> The hint bits are not really relevant when xmin = FrozenTransactionId,
> since any examiner of the tuple would cons
