Greg Smith wrote:
> On Sun, 20 May 2007, Shachar Shemesh wrote:
>
>> This is not data given to store. It's data being exported.
>
> Data being exported has a funny way of turning around and being stored
> in the database again. It's kind of nice to know the damage done
> during that round trip is
On Sun, 20 May 2007, Shachar Shemesh wrote:
This is not data given to store. It's data being exported.
Data being exported has a funny way of turning around and being stored in
the database again. It's kind of nice to know the damage done during that
round trip is minimized.
Tom seems to
On 05/19/2007 12:48:22 PM, Tom Lane wrote:
Well, but if you ask at an early stage it's perfectly fair to ask for
comments on how much work an implementation of idea X might be. Plus
people could save you from wasting time going down dead-end paths.
True. But then I wouldn't get extra points
On 5/20/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
contrib is a misnomer at best. When 8.3 branches I intend to propose
that we abandon it altogether, in line with some previous discussions.
We can change the configure help text if people think it matters that
much - which seems to me much m
Ron Mayer wrote:
Bruce Momjian wrote:
In talking to people who are assigned to review patches or could review
patches, I often get the reply, "Oh, yea, I need to do that".
Would it inspire more people to learn enough to become patch
reviewers if patch authors scheduled walkthroughs of their
pa
Koichi Suzuki <[EMAIL PROTECTED]> writes:
> As replied to "Patch queue triage" by Tom, here's simplified patch to
> mark WAL record as "compressable", with no increase in WAL itself.
> Compression/decompression commands will be posted separately to PG
> Foundary for further review.
Applied with so
Nikolay Samokhvalov wrote:
The current CVS' configure is really confusing: it has "--with-xslt"
option, while there is no XSLT support in the core. At least let's
change the option's comment to smth like "build with XSLT support (now
it is used for contrib/xml2 only)"...
contrib is a misnom
On 4/15/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Well, if we're going to make libxslt an explicit thing, then it'd be
trivial to add an xslt transformation function into the core, and then
I think we can claim equivalent support. But we'll have to check the
details, of course.
I have bee
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Comments, better ideas?
> How about building a separate Var-node for the variable when it's above
> an outer join?
[ itch... ] That would be a whole lot *more* invasive than what I'm
proposing now. It might be an interesting a
Tom Lane wrote:
Comments, better ideas?
How about building a separate Var-node for the variable when it's above
an outer join? That node would point to the original Var, and have an
additional modifier which indicates the percentage of injected nulls.
--
Heikki Linnakangas
EnterpriseDB
10 matches
Mail list logo