Thom Brown writes:
> Could we add a reference from the JSON data type page to the JSON
> functions page akin to how we do for the XML data type? Something
> like the attached patch.
Seems reasonable; committed.
regards, tom lane
--
Sent via pgsql-hackers mailing list (
On Sat, Jul 28, 2012 at 06:11:21PM +0200, Pavel Stehule wrote:
> Hello
>
> 2012/7/27 Tom Lane :
> > Pavel Stehule writes:
> >> 2012/7/26 David Fetter :
> > How about
> > \gset var1,,,var2,var3...
> >
> I don't like this - you can use fake variable - and ignoring some
> variable
Robert Haas writes:
> IMHO, the way we have it now is kind of a mess. SpinLockAcquire and
> SpinLockRelease are required to be CPU barriers, but they are not
> required to be compiler barriers. If we changed that so that they
> were required to act as barriers of both flavors,
Since they are ma
Palle Girgensohn writes:
> Hi,
> On the new Darwin 10.8 (aka mountain lion), I had to add
> #ifdef __APPLE__
> #if (__ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__ >= 1080)
> #define _XOPEN_SOURCE
> #endif
> #endif
> to the very beginning of contrib/uuid-ossp/uuid-ossp.c to get the build
> working
On Sat, Jul 28, 2012 at 6:33 PM, Jeff Janes wrote:
> A concern I have is whether the XLogCtlWrite *Write pointer needs to
> be declared volatile, to prevent the compiler from pushing operations
> on them outside of the locks (and so memory barriers) that formally
> protect them. However I see tha
Hi,
On the new Darwin 10.8 (aka mountain lion), I had to add
#ifdef __APPLE__
#if (__ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__ >= 1080)
#define _XOPEN_SOURCE
#endif
#endif
to the very beginning of contrib/uuid-ossp/uuid-ossp.c to get the build
working with --with-ossp-uuid.
I suggested someth
Adam Mackler writes:
> ... But this does not work:
> WITH outmost AS (
> SELECT 1
> UNION (WITH innermost as (SELECT 2)
> SELECT * FROM innermost
> UNION SELECT 3)
> )
> SELECT * FROM outmost;
> Result:
> ERROR: relation "innermost" does not exist
> LINE 4: SELECT
Many of you will be aware that the behaviour of commit_delay was
recently changed. Now, the delay only occurs within the group commit
leader backend, and not within each and every backend committing a
transaction:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f11e8be3e812cdbbc139c1
Hi!
Thanks for quick response.
> you can create new data types, new operators, new types of indexes if
> you want... the question is, what are you trying to do?
I want to define a new type of geographic data, as well as the PostGIS's data.
Also, my intention is to define new topological operato
On Thu, 2012-07-26 at 12:13 -0400, Bruce Momjian wrote:
> So, do we want a TODO item about adding columns to a unique index that
> will not be used for uniqueness checks?
-1 from me, at least in its current form.
At it's heart, this is about separating the constraint from the index
that enforces
On Wed, Aug 1, 2012 at 12:09 AM, Alvaro Herrera
wrote:
>
> Excerpts from Fujii Masao's message of mar jul 17 13:58:38 -0400 2012:
>
>> >> You're right. If the error is detected, that function always returns false
>> >> and the error message is emitted (but I think that current error message
>> >>
We've had a couple of complaints recently from people who were unhappy
because the syslogger's log_truncate_on_rotation logic does not fire
during the first log rotation after it's forked off from the postmaster.
The key reason for that was that to know whether to truncate or not,
the code has to k
Excerpts from Fujii Masao's message of mar jul 17 13:58:38 -0400 2012:
> >> You're right. If the error is detected, that function always returns false
> >> and the error message is emitted (but I think that current error message
> >> "pg_basebackup: child process exited with error 1" is confusing
Excerpts from Magnus Hagander's message of jue jul 12 07:35:11 -0400 2012:
> On Tue, Jul 10, 2012 at 6:45 PM, Fujii Masao wrote:
> > When an error happens after replication connection has been established,
> > pg_receivexlog doesn't close an open file descriptor and release an
> > allocated
> >
On Mon, Jul 30, 2012 at 10:26 PM, Jan Wieck wrote:
> On 7/30/2012 10:31 PM, Leon Smith wrote:
>>
>> This is not necessarily true, on multiple levels. I mean, some of
>> the programs I write are highly concurrent, and this form of batching
>> would have almost no risk of stalling the network b
Hi,
Could we add a reference from the JSON data type page to the JSON
functions page akin to how we do for the XML data type? Something
like the attached patch.
Cheers
Thom
json_docs_link.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Hi KaiGai-san,
Sorry about the delay in answering. I have been swamped with another thing
lately.
> BTW, your patch does not make sense in my environment that is just
> after initdb without any parameter customizing. Could you give us
> the step to reproduce the Nested-Loop plan from Hash-Join?
>> Based on the discussion and suggestions in this mail chain, following
>> features can be implemented:
>>
>> 1. To compute the value of max LSN in data pages based on user input whether
>> he wants it for an individual
>> file, a particular directory or whole database.
>>
>> 2a. To search t
On 30/07/12 14:33, Achim Domma wrote:
Hi,
Hi Achim,
this list is meant for discussing the development of PostgreSQL, in the
future you might want to ask your question on pgsql-general.
However, to answer your question:
I call the function like this:
select * from vectormatch(array(select
19 matches
Mail list logo
