On Tue, 2008-06-10 at 06:42 +0200, Pavel Stehule wrote:
internally is table functions implemenation identical with SRF.
It's not the internals that I'm concerned about.
Semantically is far - user's doesn't specify return type (what is from
PostgreSQL), but specifies return table, what is more
Jan Urbański wrote:
These should read TSQuery, not TSVector, no?
Yep. Applied.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
I started to look at David Fetter's patch to enable \timing on/off, in
addition to toggling the mod with just \timing.
I gather that the conclusion of the thread Making sure \timing is on,
starting at:
http://archives.postgresql.org/pgsql-general/2008-05/msg00324.php
was that we should
And here is the patch I forgot to attach.
Heikki Linnakangas wrote:
I started to look at David Fetter's patch to enable \timing on/off, in
addition to toggling the mod with just \timing.
I gather that the conclusion of the thread Making sure \timing is on,
starting at:
Right now this is not a problem because there is no insert_cleanup
function for btree, but I wonder if we should clean it up.
Look at gistbulkdelete and gistvacuumcleanup, first function wants to send a
bool flag to second one and they use GiSTBulkDelete structure instead of usual
Tom Lane wrote:
One particular case of interest is in truncate.out, where the
table-at-a-time implementation of DROP TABLE is clearly exposed
by the fact that you get multiple NOTICEs. I wonder if it would
be worth refactoring the code so that a multiple-object DROP is
implemented via
Heikki Linnakangas [EMAIL PROTECTED] writes:
I gather that the conclusion of the thread Making sure \timing is on,
starting at:
http://archives.postgresql.org/pgsql-general/2008-05/msg00324.php
was that we should leave \H and \a alone for now, because it's not clear
what \H off would do.
Pavel Stehule [EMAIL PROTECTED] writes:
what is more logical and consistent?
They're both utterly arbitrary, but the setof syntax has been in
Postgres since forever, and applies to more things than just record.
The other one doesn't fit in with anything else --- it's just a
syntactic wart.
Tom Lane escribió:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane escribi�:
(It's also worth asking where the import is coming from. Who implements
the spec syntax anyway? DB2 maybe, but when was the last time we heard
from anyone trying to migrate from DB2 to PG?)
Sourceforge?
Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
Here's a patch, based on David's patch, that turns timing into a \pset
variable, and makes \timing an alias for \pset timing. This makes
\timing behave the same as \x.
This seems a bit random to me. AFAIR all of the \pset
Heikki Linnakangas [EMAIL PROTECTED] writes:
Attached is an updated version of my patch to refactor the
XLogOpenRelation/XLogReadBuffer interface, in preparation for the
relation forks patch, and subsequently the FSM rewrite patch.
The code motion in md.c looks fairly bogus; was that a
On Mon, 2008-06-09 at 00:25 -0700, Neil Conway wrote:
Attached is a patch that makes some minor changes to the text emitted by
the new help command.
Applied to HEAD.
-Neil
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
12 matches
Mail list logo
