This is indeed really cool. I'm sorry I haven't gotten to doing what I
promised in this area but I'm glad it's happening anyways.
"Zoltan Boszormenyi" <[EMAIL PROTECTED]> writes:
> Can we get the rows in tree order, please?
>...
> After all, I didn't specify any ORDER BY clauses in the base, r
"David Fetter" <[EMAIL PROTECTED]> writes:
> On Mon, May 19, 2008 at 12:21:20AM -0400, Gregory Stark wrote:
>> "Zoltan Boszormenyi" <[EMAIL PROTECTED]> writes:
>> > Also, it seems there are no infinite recursion detection:
>> >
>> > # with recursive x(level, parent, child) as (
>> >select 1::i
On Sunday 18 May 2008 03:18:13 Greg Smith wrote:
> On Sat, 17 May 2008, Robert Lor wrote:
> > I'd like to propose adding the following probes (some of which came from
> > Simon) to 8.4.
>
> There's also a big DTrace probe set patch available from OmniTI:
> https://labs.omniti.com/project-dtrace/tru
On Mon, May 19, 2008 at 12:21:20AM -0400, Gregory Stark wrote:
> "Zoltan Boszormenyi" <[EMAIL PROTECTED]> writes:
> > Also, it seems there are no infinite recursion detection:
> >
> > # with recursive x(level, parent, child) as (
> >select 1::integer, * from test_connect_by where parent is null
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I've been testing a new patch and do not see the problem on Fedora 8,
>> so at least that platform's readline seems to be fixed.
> It broke my FC6 box :-(
Yeah, I saw. I'm inclined to wait a day to get a handle on the scope
of the p
Merlin Moncure wrote:
On Sun, May 18, 2008 at 5:22 PM, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
Can we get the rows in tree order, please? I.e. something like this:
Is ordering by tree order defined in the standard when no explicit
order is given? If not, it probably returns them
On Sun, May 18, 2008 at 5:22 PM, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
> Can we get the rows in tree order, please? I.e. something like this:
Is ordering by tree order defined in the standard when no explicit
order is given? If not, it probably returns them in the order they
are pulled up
Tom Lane wrote:
I've been testing a new patch and do not see the problem on Fedora 8,
so at least that platform's readline seems to be fixed. I find
the hack Martijn proposes in the above message to be pretty ugly,
so what I'm inclined to do is leave that out for now and see what
failures we g
David Fetter írta:
On Sun, May 18, 2008 at 08:51:29PM +0900, Tatsuo Ishii wrote:
WITH RECURSIVE patch V0.1
Here are patches to implement WITH RECURSIVE clause. There are some
limitiations and TODO items(see the "Current limitations" section
below). Comments are welcome.
1. Credit
These pat
On Sun, May 18, 2008 at 1:38 PM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
> I don't know how you tested,
Copy a large file across a relatively slow network, and check the size
on the destination drive before it finishes.
> but could you please repeat the test with
> GnuWin32's cp.exe? If it do
Greg Smith wrote:
There's also a big DTrace probe set patch available from OmniTI:
https://labs.omniti.com/project-dtrace/trunk/postgresql/
http://labs.omniti.com/trac/project-dtrace/wiki/Applications#PostgreSQL
I don't know if you've looked at that before. There's some overlap
but many uniq
Have any Windows-using hackers tried to look into the reports of
$SUBJECT on 8.3? We have two fresh reports:
http://archives.postgresql.org/pgsql-bugs/2008-05/msg00106.php
http://archives.postgresql.org/pgsql-bugs/2008-05/msg00109.php
and this isn't the first time we've heard of it.
I spent some
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
I suggest:
pg_listened_events(out event name) returns setof record
pg_pending_events(out event name, out message text) returns setof record
The first would show events being listened on by the current backend,
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I suggest:
> pg_listened_events(out event name) returns setof record
> pg_pending_events(out event name, out message text) returns setof record
> The first would show events being listened on by the current backend,
> while the second would show all
I am working on moving the notification buffer into shared memory as
previously discussed. Since pg_listener will no longer exist, I think we
need to provide a couple of information functions.
I suggest:
pg_listened_events(out event name) returns setof record
pg_pending_events(out event nam
On Sun, May 18, 2008 at 08:51:29PM +0900, Tatsuo Ishii wrote:
> WITH RECURSIVE patch V0.1
>
> Here are patches to implement WITH RECURSIVE clause. There are some
> limitiations and TODO items(see the "Current limitations" section
> below). Comments are welcome.
>
> 1. Credit
>
> These patches we
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Recently while adding $PostgreSQL markers to a bunch of .c and .h files
I ran into trouble with the ecpg regression tests and had to revert the
change for a handful of files. However, it occurred to me that we could
have pg_regres
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Recently while adding $PostgreSQL markers to a bunch of .c and .h files
> I ran into trouble with the ecpg regression tests and had to revert the
> change for a handful of files. However, it occurred to me that we could
> have pg_regress tell diff to
Recently while adding $PostgreSQL markers to a bunch of .c and .h files
I ran into trouble with the ecpg regression tests and had to revert the
change for a handful of files. However, it occurred to me that we could
have pg_regress tell diff to ignore such lines, by passing it the
arguments "
On Thu, 15 May 2008, Nikhils wrote:
On Thu, May 15, 2008 at 11:59 AM, Pavel Stehule <[EMAIL PROTECTED]>
wrote:
I always use a ~/.cvsrc containing
My .cvsrc also includes:
Good hints, and there's now a little section including them all at
http://wiki.postgresql.org/wiki/Working_with_CVS#Init
Dave Page wrote:
On Tue, May 13, 2008 at 5:11 PM, Alvaro Herrera
<[EMAIL PROTECTED]> wrote:
Andrew Dunstan wrote:
> I would be very surprised if xcopy did not exhibit the same
> preallocating behaviour as copy.
I, on the other hand, would not say anything until someone tried it, and
t
On Sat, 17 May 2008, Robert Lor wrote:
I'd like to propose adding the following probes (some of which came from
Simon) to 8.4.
There's also a big DTrace probe set patch available from OmniTI:
https://labs.omniti.com/project-dtrace/trunk/postgresql/
http://labs.omniti.com/trac/project-dtrace/
22 matches
Mail list logo
