Hi,
Le 10 août 09 à 17:19, Andrew Dunstan a écrit :
One fairly simple way would use a new SQL verb (say, DO) like this:
DO $$ something in plfoo$ $ LANGUAGE plfoo;
We could even default the langauge to plpgsql, for which you would
then just need:
DO $$ something in plpgsql $$;
That
2009/8/15 Dimitri Fontaine dfonta...@hi-media.com:
Hi,
Le 10 août 09 à 17:19, Andrew Dunstan a écrit :
One fairly simple way would use a new SQL verb (say, DO) like this:
DO $$ something in plfoo$ $ LANGUAGE plfoo;
We could even default the langauge to plpgsql, for which you would then
Pavel Stehule wrote:
why we need DO statement? Why not just $$ $$. Only string literal
cannot be statement too, so DO is unnecessary.
it can look like:
$$
FOR r IN SELECT
END LOOP;
$$;
???
Well, it's arguably somewhat un-SQL-ish. Every command in SQL is
introduced by a
2009/8/15 Andrew Dunstan and...@dunslane.net:
Pavel Stehule wrote:
why we need DO statement? Why not just $$ $$. Only string literal
cannot be statement too, so DO is unnecessary.
it can look like:
$$
FOR r IN SELECT
END LOOP;
$$;
???
Well, it's arguably somewhat
Andrew Dunstan and...@dunslane.net writes:
Pavel Stehule wrote:
why we need DO statement? Why not just $$ $$. Only string literal
cannot be statement too, so DO is unnecessary.
I'm also not sure I want to be trying to execute any arbitrary string
that accidentally gets placed there because
Hi,
[ CC'ing to the postgres-r mailing list ]
Mark Mielke wrote:
On 08/12/2009 12:04 PM, Suno Ano wrote:
can anybody tell me, is there a roadmap with regards to
http://www.postgres-r.org ?
I'm glad you're asking.
I would love to see it become production-ready asap.
Yes, me too. Do you
problem is that PostgreSQL uses ossp UUID which is not integrated in
OpenSolaris. Solaris has own uuid implementation which seems to me similar
but not same. Try man uuid_generate or less /usr/uuid/uuid.h
That's really interesting. I'll try this.
It should be easy to port it but it needs a
Thinking about window function performance improvement as well as
concerning about GROUPING SETS discussed a couple of days before, I
wonder why we have both of tuplestore and tuplesort. They are very
similar but have different functions such as multiple read pointer
with tuplestore whereas
Hitoshi Harada umi.tan...@gmail.com writes:
Looking for git/cvs log a bit, tuplesort was already there since 1999
while tuplestore was introduced around 2000 for materialized node. Why
then was tuplestore invented as a new feature instead of extending
tuplesort? Can't we unit them now?
I
2009/8/16 Tom Lane t...@sss.pgh.pa.us:
Hitoshi Harada umi.tan...@gmail.com writes:
Looking for git/cvs log a bit, tuplesort was already there since 1999
while tuplestore was introduced around 2000 for materialized node. Why
then was tuplestore invented as a new feature instead of extending
I'm also not sure I want to be trying to execute any arbitrary string
that accidentally gets placed there because someone forgot to put a
keyword or accidentally deleted it.
But I'm not too dogmatic on the subject. What do others think?
Given that $$ is also used to quote non-procedural
2009/8/16 Hitoshi Harada umi.tan...@gmail.com:
2009/8/16 Tom Lane t...@sss.pgh.pa.us:
Hitoshi Harada umi.tan...@gmail.com writes:
Looking for git/cvs log a bit, tuplesort was already there since 1999
while tuplestore was introduced around 2000 for materialized node. Why
then was tuplestore
Le 15 août 09 à 22:49, Josh Berkus a écrit :
Ideally, we'd be able to execute *any* PL that way by setting a shell
variable:
\pl plperl
DO $f$ foreach ( @_ ) { ...
Nitpicking dept, I think I prefer:
DO [ [LANGUAGE] language] $$ ... $$;
DO plperl $$ ... $$;
DO language plpython $$ ... $$;
On Sat, Aug 15, 2009 at 11:34:04PM +0200, Dimitri Fontaine wrote:
Nitpicking dept, I think I prefer:
DO [ [LANGUAGE] language] $$ ... $$;
DO plperl $$ ... $$;
DO language plpython $$ ... $$;
language is optional and defaults to plpgsql.
Yup, sounds nicer. The less globals the better!
Josh Berkus wrote:
I'm also not sure I want to be trying to execute any arbitrary string
that accidentally gets placed there because someone forgot to put a
keyword or accidentally deleted it.
But I'm not too dogmatic on the subject. What do others think?
Given that $$ is also used to
On fre, 2009-08-14 at 13:57 -0700, Jeff Davis wrote:
Looking at the definitions of vacuum_freeze_min_age and
autovacuum_freeze_max_age there seems to be almost no distinction
between min and max in those two names.
For min, the action happens at or above the min values. For max, the
action
Bruce Momjian wrote:
Log Message:
---
Remove tabs from SGML.
Tags:
REL8_3_STABLE
Modified Files:
--
pgsql/doc/src/sgml/ref:
psql-ref.sgml (r1.198.2.1 - r1.198.2.2)
On lör, 2009-08-15 at 23:31 +0100, Sam Mason wrote:
On Sat, Aug 15, 2009 at 11:34:04PM +0200, Dimitri Fontaine wrote:
Nitpicking dept, I think I prefer:
DO [ [LANGUAGE] language] $$ ... $$;
DO plperl $$ ... $$;
DO language plpython $$ ... $$;
language is optional and defaults
On lör, 2009-08-15 at 19:13 -0400, Andrew Dunstan wrote:
Do we have some recommended emacs settings for editing the docs? Do we
need a pgsql-docs mode?
There are suggested settings in src/tools/editors/emacs.samples .
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Peter Eisentraut wrote:
On lör, 2009-08-15 at 19:13 -0400, Andrew Dunstan wrote:
Do we have some recommended emacs settings for editing the docs? Do we
need a pgsql-docs mode?
There are suggested settings in src/tools/editors/emacs.samples .
Thanks. I wonder how I missed that.
On tis, 2009-05-26 at 16:07 -0700, Caleb Welton wrote:
Patch for plpythonu
Primary motivation of the attached patch is to support handling bytea
conversion allowing for embedded nulls, which in turn allows for
supporting the marshal module.
Secondary motivation is slightly improved
Andrew Dunstan wrote:
Bruce Momjian wrote:
Log Message:
---
Remove tabs from SGML.
Tags:
REL8_3_STABLE
Modified Files:
--
pgsql/doc/src/sgml/ref:
psql-ref.sgml (r1.198.2.1 - r1.198.2.2)
On Sun, 2009-08-16 at 02:02 +0300, Peter Eisentraut wrote:
For min, the action happens at or above the min values. For max, the
action happens at or below the max value.
From the docs, 23.1.4:
autovacuum is invoked on any table that might contain XIDs older than
the age specified by the
Bruce Momjian wrote:
Andrew Dunstan wrote:
Bruce Momjian wrote:
Log Message:
---
Remove tabs from SGML.
Tags:
REL8_3_STABLE
Modified Files:
--
pgsql/doc/src/sgml/ref:
psql-ref.sgml (r1.198.2.1 - r1.198.2.2)
On Sat, Aug 15, 2009 at 07:13:42PM -0400, Andrew Dunstan wrote:
Bruce Momjian wrote:
Log Message:
---
Remove tabs from SGML.
Tags:
REL8_3_STABLE
Modified Files:
--
pgsql/doc/src/sgml/ref:
psql-ref.sgml (r1.198.2.1 - r1.198.2.2)
On Sun, Aug 16, 2009 at 02:15:39AM +0300, Peter Eisentraut wrote:
On 2009-08-15 at 23:31 +0100, Sam Mason wrote:
Next all you need is to be able to PREPARE them (and somehow access the
parameters from execute) and you'll have nice local functions. :)
Yeah, rather than just making up some
On Sat, Aug 15, 2009 at 7:15 PM, Peter Eisentrautpete...@gmx.net wrote:
On lör, 2009-08-15 at 23:31 +0100, Sam Mason wrote:
On Sat, Aug 15, 2009 at 11:34:04PM +0200, Dimitri Fontaine wrote:
Nitpicking dept, I think I prefer:
DO [ [LANGUAGE] language] $$ ... $$;
DO plperl $$ ... $$;
Robert Haas wrote:
I like this idea (although it might not be too easy to implement, not
sure), but I think we could still use DO (which is shorter) for the
verb. Lambda-calculus is cool, but do is nice and simple.
SQL is not Lisp. Simple is good. I didn't think Peter was really very
28 matches
Mail list logo
