Hello,
I am working on scrollable cursors, and MOVE statement has relation to it.
Regards
Pavel Stehule
_
Chcete sdilet sve obrazky a hudbu s prateli? http://messenger.msn.cz/
---(end of
Peter Eisentraut wrote:
SQL/PSM default for SQL procedures are SECURITY DEFINER (like views),
I can't find this in the standard. Where did you get this
information?
I only have a draft version of SQL:2003, which says in the 'Foundation'
book, chapter 11.50 (SQL-invoked routine), about the
Am Montag, 8. Januar 2007 05:10 schrieb Bruce Momjian:
Here is a patch that runs the build twice when HTML.index does not
exist, and once every time after that. This is not ideal, but it is a
start.
The problem is that this requires two runs even to proof the documentation,
which I think no
Bruce Momjian wrote:
Simon Riggs wrote:
All have been awaiting review for at least a month (though in one case
the latest version is quite recent). They probably ought to be on the
hold queue; all are ready to be reviewed for final
application/rejection.
I'd hasten to add that none of those
Bruce Momjian wrote:
I saw no replies to this.
Sounds like a good idea to me.
(further comments below)
Simon Riggs wrote:
Implementing the variable mark/restore buffer as a dumb Tuplestore would
mean that the space usage of the Sort could in worst case go as high as
x2 total space. The
Dave Page wrote:
I don't object to it in principle, but I think a bit more thought is
needed as to what's the goal. A stupid append option would be enough
for pg_dumpall's current capabilities (ie, text output only) --- but is
it reasonable to consider generalizing -Fc and -Ft modes to deal
One problem with only putting this information in the system logs
is that when we provide database services to a member of our
community we do not actually give them an account of the DB server
or log server. This means that this very useful information would
need to be passed through an
Ühel kenal päeval, K, 2006-12-27 kell 14:06, kirjutas David Fetter:
Folks,
While using DBI-Link, I've noticed a little lacuna in how functions
returning (SETOF) RECORD work, namely, that you have to cast them to
explicit lists of columns, even when that list of columns corresponds
to an
Simon Riggs wrote:
On Sat, 2007-01-06 at 16:08 -0500, Bruce Momjian wrote:
I have looked over this patch, and it completes part of this TODO item:
o Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
ANALYZE, and CLUSTER
It involves a patch to the
Heikki Linnakangas wrote:
Bruce Momjian wrote:
Simon Riggs wrote:
All have been awaiting review for at least a month (though in one case
the latest version is quite recent). They probably ought to be on the
hold queue; all are ready to be reviewed for final
application/rejection.
Jonathan Hull [EMAIL PROTECTED] writes:
The key feature for the error is that when a result structure (eg : pg_foo)
is defined with a domain type that is not null, only PG 8.2 errors if the
result is an empty set.
The problem is explained well enough by this comment in plpgsql's code
for
Bruce Momjian wrote:
Right, because even the decision of whether they should be in the queue
is a decision for us. The hold queue additions are less stringent than
the main patch queue.
Isn't that always the case though, not just after FF when the hold queue
starts getting activity again?
On Mon, 2007-01-08 at 11:28 -0500, Bruce Momjian wrote:
Simon Riggs wrote:
On Sat, 2007-01-06 at 16:08 -0500, Bruce Momjian wrote:
I have looked over this patch, and it completes part of this TODO item:
o Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
Bruce Momjian wrote:
Heikki Linnakangas wrote:
Bruce Momjian wrote:
Simon Riggs wrote:
All have been awaiting review for at least a month (though in one case
the latest version is quite recent). They probably ought to be on the
hold queue; all are ready to be reviewed for final
Heikki Linnakangas wrote:
I'm confused,
So I see.
I thought the difference between the pgpatches queue and
the pgpatches_hold queue is the release the patch is targeted for. If
there's a third queue for patches that need review before being added to
another queue, could we have that
Simon Riggs [EMAIL PROTECTED] writes:
On Mon, 2007-01-08 at 11:28 -0500, Bruce Momjian wrote:
The complex part of this is that the feature requires patches to the
backend, and has a /contrib component.
The plugin approach is exactly what happened with the debugger. The
backend has an
Andrew Dunstan wrote:
The latter does not exist, AFAIK. Before feature freeze for cycle X, we
don't usually hold patches for release X+1, as I understand it.
In general, we should try to hold patches as little amount of time as
possible. That way they don't go stale as easily.
I did not
Heikki Linnakangas wrote:
Bruce Momjian wrote:
Heikki Linnakangas wrote:
Bruce Momjian wrote:
Simon Riggs wrote:
All have been awaiting review for at least a month (though in one case
the latest version is quite recent). They probably ought to be on the
hold queue; all are ready to be
On Mon, Jan 08, 2007 at 10:37:25AM +, Heikki Linnakangas wrote:
Simon Riggs wrote:
Implementing the variable mark/restore buffer as a dumb Tuplestore would
mean that the space usage of the Sort could in worst case go as high as
x2 total space. The worst case is where the inner scan is all
On Sun, 7 Jan 2007 21:04:09 -0800 (PST)
Jeremy Drake [EMAIL PROTECTED] wrote:
This commit message is rather old, I remarked on its absence earlier, but
better late than never I guess ;)
Not sure what you mean. I just committed it recently. I held off
until after the release as requested.
one of my new buildfarm boxes (an Debian/Etch based ARM box) is
sometimes failing to stop the database during the regression tests:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=quaggadt=2007-01-08%2003:03:03
this only seems to happen sometimes and only if --with-tcl is enabled on
On Fri, Jan 05, 2007 at 08:05:26PM +, Dave Page wrote:
Andreas Pflug wrote:
Dave Page wrote:
In pgAdmin we use pg_dump's -f option to write backup files. The IO
streams are redirected to display status and errors etc. in the GUI.
In order to enhance the interface to allow backup of
Devrim GUNDUZ wrote:
-- Start of PGP signed section.
Hi Bruce,
On Mon, 2007-01-08 at 11:35 -0500, Bruce Momjian wrote:
OK, naming suggestions?
BTW, why do you keep those pages in your homepage, but not in
postgresql.org? Just wondering.
--and personally, I'd prefer to see them in
Jim C. Nasby wrote:
It might make sense to provide a programmatic interface to pg_dump to
provide tools like pgAdmin more flexibility.
Are you talking about pg_dump in a lib? Certainly a good idea, because
it allows better integration (e.g. progress bar).
But it certainly doesn't make sense
There was some discussion recently of simplifying the sorting code (and
hopefully making it a tad faster) by eliminating support for using
randomly-chosen operators in ORDER BY ... USING, and requiring USING to
specify an operator that is the or member of some btree opclass.
This strikes me as a
Bruce Momjian [EMAIL PROTECTED] writes:
Peter Eisentraut wrote:
The problem is that this requires two runs even to proof the documentation,
which I think no one wants.
So what would the API be to signal you want a draft build?
gmake DRAFT=Y html
I'd vote for
gmake draft
On Fri, Jan 05, 2007 at 11:02:32PM -0600, Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Jim Nasby wrote:
More important, I see no reason to tie applying patches to pulling
from CVS. In fact, I think it's a bad idea: you want to build just
what's in CVS
Happy new year
From: Simon Riggs [EMAIL PROTECTED]
Have you tried setting deadline scheduler on the WAL device and CFQ
on
the data device? That should allow the I/Os to move through
different
queues and prevent interference.
No, I've not tried yet. Inaam-san told me that Linux had a few I/O
It looks like pltcl regression tests are failing due to the recent ORDER
BY ... USING change.
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=mongoosedt=2007-01-09%2002:30:01
--
Horse sense is the thing a horse has which keeps it from betting on
people.
-- W. C. Fields
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
one of my new buildfarm boxes (an Debian/Etch based ARM box) is
sometimes failing to stop the database during the regression tests:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=quaggadt=2007-01-08%2003:03:03
this only seems to happen
On 1/8/07, Tom Lane [EMAIL PROTECTED] wrote:
(This is not a statement that I approve of the specific plugin hooks
proposed --- I don't particularly. But if we can come up with something
a bit cleaner, that's how I'd approach it.)
I have another idea for making the hooks a bit more cleaner;
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Peter Eisentraut wrote:
The problem is that this requires two runs even to proof the documentation,
which I think no one wants.
So what would the API be to signal you want a draft build?
gmake DRAFT=Y html
I'd vote for
Pavel Stehule wrote:
Hello,
I am working on scrollable cursors, and MOVE statement has relation to it.
You mean we should add MOVE to pl/pgsql. Yes, still on the TODO list,
and I don't think it is completed --- not sure why it is so hard.
--
Bruce Momjian [EMAIL PROTECTED]
D'Arcy J.M. Cain wrote:
On Sun, 7 Jan 2007 21:04:09 -0800 (PST)
Jeremy Drake [EMAIL PROTECTED] wrote:
This commit message is rather old, I remarked on its absence earlier, but
better late than never I guess ;)
Not sure what you mean. I just committed it recently. I held off
until after
On Jan 8, 2007, at 19:25 , Jim C. Nasby wrote:
Actually, I see point in both... I'd think you'd want to know if a
patch
worked against the CVS checkout it was written against.
Regardless, it's unlikely that the patch was tested against all of
the platforms available on the build farm. If
Pavel Stehule wrote:
Hello,
I am working on scrollable cursors, and MOVE statement has relation to
it.
You mean we should add MOVE to pl/pgsql. Yes, still on the TODO list,
and I don't think it is completed --- not sure why it is so hard.
--
It's simply task, but it needs some enhanced
This commit message is rather old, I remarked on its absence earlier, but
better late than never I guess ;)
Not sure what you mean. I just committed it recently. I held off
until after the release as requested. What do you mean by old?
You committed it five days ago, because the
Magnus Hagander [EMAIL PROTECTED] writes:
i'm sure it got stuck in the maia filter (happens all the time with
delays of a couple of hours up to several days) or in the moderator
steve (if the sender was'nt on the list allow. can happen since it was
a long time since he last committed).
D'Arcy
Tom Lane wrote:
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
one of my new buildfarm boxes (an Debian/Etch based ARM box) is
sometimes failing to stop the database during the regression tests:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=quaggadt=2007-01-08%2003:03:03
this
Magnus Hagander [EMAIL PROTECTED] writes:
Attached is a simple README file (part from Dave P, if my memory is not
mistaken) for the vcbuild stuff. Please put in src/tools/msvc.
Applied, with Mark K's fix and a bit of polishing of my own.
regards, tom lane
Magnus Hagander [EMAIL PROTECTED] writes:
This patch fixes vcbuild so you can build without OpenSSL and libz
should you want to. This disables the sslinfo and pgcrypto modules
because they require the libraries to build at all.
Applied.
regards, tom lane
41 matches
Mail list logo
