[ Sorry, removed previous version of patch from queue.]
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Neil Conway wrote:
> [EMAIL PROTECTED] writes:
Thomas Lockhart wrote:
> ...
> > > > Hard to imagine why anyone would want such an optimization. How much
> > > > faster could it possibly be?
> > > Back in ye bad olde days, there was probably an order-of-magnitude
> > > difference between the speed of a float multiply and that of a float
> > >
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> with -ffast-math gcc will "improve" it to
> >>
> >> int hour = time * 0.000278;
>
> > Hard to imagine why anyone would want such an optimization. How much
> > faster could it possibly be?
>
> Back
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> with -ffast-math gcc will "improve" it to
>>
>> int hour = time * 0.000278;
> Hard to imagine why anyone would want such an optimization. How much
> faster could it possibly be?
Back in ye bad olde days, there was proba
Tom Lane wrote:
> Ron Johnson <[EMAIL PROTECTED]> writes:
> > Out of curiosity: why does -ffast-math break the datetime rounding code?
>
> We dug into this last night, and it turns out that the culprit is code
> like
>
> int hour = time / 3600;
>
> where time is a double. This yields an
Ron Johnson <[EMAIL PROTECTED]> writes:
> Out of curiosity: why does -ffast-math break the datetime rounding code?
We dug into this last night, and it turns out that the culprit is code
like
int hour = time / 3600;
where time is a double. This yields an exact result when done
correctly
"marc persuy" <[EMAIL PROTECTED]> writes:
> what I mean is if I use a rule to execute any action,
> the rule should report an error to the client if, for any reason, this
> action fails.
It does.
> inserting into my_view will always return a sucess condition,
> even if you try to use it to inser
[EMAIL PROTECTED] writes:
> If you try to use rules to implement update and insert on views, these
> rules do not report any error neither on insert nor on update action.
I see nothing in here that should raise an error.
> the tiers view shows all datas from user and his/her partners, is
> suppo
marc persuy ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
rewrite rules on update or insert do not report errors
Long Description
If you try to use rules to implement update and insert on views, these
rules do not report any
10 matches
Mail list logo
