On Sat, 2009-02-28 at 23:21 -0800, Josh Berkus wrote:
Fujii,
Again, I'm not planning to get rid of any existing capabilities
Good
unless necessary.
That is not a caveat I will accept, a priori.
While Simon stated it a bit strongly
My intention was only to be clear about
Fujii,
Again, I'm not planning to get rid of any existing capabilities
Good
unless necessary.
That is not a caveat I will accept, a priori.
While Simon stated it a bit strongly, I think it's important that you
alert people if you think you have to remove existing features in order
to
On 1 Mar 2009, at 00:52, Andrew Dunstan wrote:
We seem to have acquired a cardinality() function with almost no
discussion, and it has semantics that are a bit surprising to me. I
should have thought cardinality(array) would be the total number of
elements in the array. Instead, it
Hi Teodor-san.
Sorry late reaction.
- Original Message -
From: Teodor Sigaev teo...@sigaev.ru
If there's an effective function like pg_wchar2mb_with_len() which
converts wchar_t strings to server encoded strings, we had better
simply call it for char2wchar().
I don't see a way to
Hannu Krosing wrote:
Some of the functions, including some specified in the standard, produce
fragments. That's why we have the 'IS DOCUMENT' test.
But then you could use xmlfragments as the functions return type, no ?
Does tha standard require that the same field type must store both
Grzegorz Jaskiewicz wrote:
On 1 Mar 2009, at 00:52, Andrew Dunstan wrote:
We seem to have acquired a cardinality() function with almost no
discussion, and it has semantics that are a bit surprising to me. I
should have thought cardinality(array) would be the total number of
elements in
Andrew Dunstan and...@dunslane.net writes:
Grzegorz Jaskiewicz wrote:
On 1 Mar 2009, at 00:52, Andrew Dunstan wrote:
We seem to have acquired a cardinality() function with almost no
discussion, and it has semantics that are a bit surprising to me. I
should have thought cardinality(array)
I wrote:
The standard doesn't have multi-dimensional arrays, so it's entirely
possible that somewhere in it there is wording that makes cardinality()
equivalent to the length of the first dimension. But I concur with
Andrew that this is flat wrong when extended to m-d arrays.
I poked around
2009/3/1 Tom Lane t...@sss.pgh.pa.us:
I wrote:
The standard doesn't have multi-dimensional arrays, so it's entirely
possible that somewhere in it there is wording that makes cardinality()
equivalent to the length of the first dimension. But I concur with
Andrew that this is flat wrong when
Tom Lane wrote:
The REL7_4 members of the buildfarm are all red this morning,
with this symptom in initdb:
Oh dear. I must confess that I didn't test the 7.4 commit, because the
7.4 branch isn't compiling on my laptop for some reason. Seemed safe
enough since the changed codepath hadn't been
On Sun, 1 Mar 2009, Tom Lane wrote:
I wrote:
The standard doesn't have multi-dimensional arrays, so it's entirely
possible that somewhere in it there is wording that makes cardinality()
equivalent to the length of the first dimension. But I concur with
Andrew that this is flat wrong
On Sunday 01 March 2009 19:40:16 Tom Lane wrote:
I wrote:
The standard doesn't have multi-dimensional arrays, so it's entirely
possible that somewhere in it there is wording that makes cardinality()
equivalent to the length of the first dimension. But I concur with
Andrew that this is
FragmentDelimiter is an argument for ts_headline function to separates
different headline fragments. The default delimiter is ... .
Currently if someone specifies the delimiter as an option to the
function, no extra space is added around the delimiter. However, it does
not look good without space
On Sun, 2009-03-01 at 10:13 -0500, Andrew Dunstan wrote:
Hannu Krosing wrote:
Some of the functions, including some specified in the standard, produce
fragments. That's why we have the 'IS DOCUMENT' test.
But then you could use xmlfragments as the functions return type, no ?
Hannu Krosing wrote:
On Sun, 2009-03-01 at 10:13 -0500, Andrew Dunstan wrote:
Hannu Krosing wrote:
Some of the functions, including some specified in the standard, produce
fragments. That's why we have the 'IS DOCUMENT' test.
But then you could use xmlfragments as the
Peter Eisentraut pete...@gmx.net writes:
The standard represents multidimensional arrays as arrays of arrays (like in
C).
Uh, C doesn't represent multidimensional arrays as arrays of arrays so you've
lost me already.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Gregory Stark wrote:
Peter Eisentraut pete...@gmx.net writes:
The standard represents multidimensional arrays as arrays of arrays (like
in
C).
Uh, C doesn't represent multidimensional arrays as arrays of arrays so you've
lost me already.
I think he meant to say C _can_ represent
Sushant Sinha sushant...@gmail.com writes:
FragmentDelimiter is an argument for ts_headline function to separates
different headline fragments. The default delimiter is ... .
Currently if someone specifies the delimiter as an option to the
function, no extra space is added around the
Pavel Stehule pavel.steh...@gmail.com writes:
postgres=# create function dfunc(a int, b int = 1, c int) returns
table (a int, b int, c int) as $$
select $1, $2, $3;
$$ language sql;
The above is simply a horrid idea. It'll completely break any ability
to resolve ambiguous function calls in
Hi,
On Sun, Mar 1, 2009 at 4:21 PM, Josh Berkus j...@agliodbs.com wrote:
While Simon stated it a bit strongly, I think it's important that you alert
people if you think you have to remove existing features in order to make
easy standby possible.
Now, I think that any existing capabilities
yeah you are right. I did not know that you can pass space using double
quotes.
-Sushant.
On Sun, 2009-03-01 at 20:49 -0500, Tom Lane wrote:
Sushant Sinha sushant...@gmail.com writes:
FragmentDelimiter is an argument for ts_headline function to separates
different headline fragments. The
Hi,
On Fri, Feb 27, 2009 at 6:52 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
We're using SIGQUIT to signal immediate shutdown request. Upon receiving
SIGQUIT, postmaster in turn kills all the child processes with SIGQUIT and
exits.
This is a problem when child processes
2009/3/2 Tom Lane t...@sss.pgh.pa.us:
Pavel Stehule pavel.steh...@gmail.com writes:
postgres=# create function dfunc(a int, b int = 1, c int) returns
table (a int, b int, c int) as $$
select $1, $2, $3;
$$ language sql;
The above is simply a horrid idea. It'll completely break any
23 matches
Mail list logo
