Neil Conway said:
> On Tue, 2006-02-28 at 22:38 -0500, Tom Lane wrote:
>> There are one or two "cannot"s that should be "could not"s in your hit
>> list, per the style guidelines.
>>
>> While you're at it -- I noticed several of the tsearch2 messages refer
>> to "lexem(s)". The word is "lexeme", t
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> (side note - maybe we need a check target for these that uses a temp install
> - that would make it easier to check for errors like this).
IIRC, the reason we don't have that is that it's too hard to get it to
work reliably (shared library search path
Mark Dilger wrote:
Mark Dilger wrote:
Tom Lane wrote:
"Milen A. Radev" <[EMAIL PROTECTED]> writes:
Milorad Poluga напи�а:
SELECT '10 years 1 mons 1 days'::interval - '9 years 10 mons 15
days'::interval
?column?--- 3 mons -14 days
Why not '2 mons 16 days' ?
On Feb 11 11:24, Bruce Momjian wrote:
> I have updated the patch to match CVS (attached), but am seeing the
> following regression differences where the COPY error messages are now
> missing.
I've revised the patch (attached) and now it seems to be ok - passes
regression tests too. Any other comme
Robert Treat wrote:
> On Thursday 16 February 2006 00:27, Tom Lane wrote:
> > Robert Treat <[EMAIL PROTECTED]> writes:
> > > As stated, the following patch adds a list of patch submission guidelines
> > > based on Simon Riggs suggestions to the developers FAQ.
> >
> > A couple minor comments ...
>
Is this patch going to be applied?
---
Andrew Dunstan wrote:
>
>
> Dmitry Karasik wrote:
>
> [patch snipped]
>
> I have cleaned this patch somewhat by removing some bitrot that occurred
> since it was submitted, and adj
I am waiting for an update from Dmitry.
cheers
andrew
Bruce Momjian wrote:
Is this patch going to be applied?
---
Andrew Dunstan wrote:
I have cleaned this patch somewhat by removing some bitrot that occurred
si
> Bruce Momjian wrote:
> >Is this patch going to be applied?
> I am waiting for an update from Dmitry.
> cheers
> andrew
I believe this is some kind of misunderstanding, sorry if from my part,
but I don't think any further updates are necessary.
> >>But why do we have to call spi_freeplan? pltcl,