On 16 March 2014 11:55, Tom Lane wrote:
> Our documentation claims that the minimum Python version for plpython
> is 2.3. However, an attempt to build with that on an old Mac yielded
> a bunch of failures in the plpython_types regression test, all of the
> form
>
...
> Personally I have no desire
eFrom: "Tom Lane"
After some discussion, the core committee has concluded that the
WAL-replay bug fixed in commit 6bfa88acd3df830a5f7e8677c13512b1b50ae813
is indeed bad enough to justify near-term update releases. Since
there seems no point in being slow about it, tarballs will be wrapped
Monda
On 15.3.2014 02:15, Peter Geoghegan wrote:
> On Fri, Mar 14, 2014 at 5:10 PM, Tomas Vondra wrote:
>> I'm on commit a3115f0d, which is just 2 days old, so I suppose this was
>> not fixed yet.
>
> Try merging the feature branch now, which will get you commit 16923d,
> which you're missing. That was
On 11/28/2013 09:15 AM, Tom Dunstan wrote: > Feature Proposal: Selective
foreign keys. > - > Allow
foreign keys to have where clauses.
I like this feature. One of the issues I have been trying to deal with is how
to model countries and their subdi
On Fri, Mar 14, 2014 at 4:43 PM, Tom Lane wrote:
> Whilst setting up a buildfarm member on an old, now-spare Mac, I was
> somewhat astonished to discover that contrib/test_shm_mq crashes thus:
> TRAP: FailedAssertion("!(rb >= sizeof(uint64))", File: "shm_mq.c", Line: 429)
> but only in UTF8 locale
Our documentation claims that the minimum Python version for plpython
is 2.3. However, an attempt to build with that on an old Mac yielded
a bunch of failures in the plpython_types regression test, all of the
form
! ERROR: could not import a module for Decimal constructor
! DETAIL: ImportError:
On Sat, Mar 15, 2014 at 11:27 PM, Heikki Linnakangas <
hlinnakan...@vmware.com> wrote:
> On 03/15/2014 08:40 PM, Fujii Masao wrote:
>
>> Hi,
>>
>> I executed the following statements in HEAD and 9.3, and compared
>> the size of WAL which were generated by data insertion in GIN index.
>>
>> ---
Hi!
On Thu, Mar 6, 2014 at 6:59 AM, Alex Hunsaker wrote:
. . .
> This will apply cleanly all the way to REL9_2_STABLE. It applies (with
> fuzz, but cleanly to REL9_1). REL9_0 does this completely differently
> and so does not have this leak.
>
Looks like patch still not pushed to repo.
--
Ser
First-draft release notes are committed, and should be visible at
http://www.postgresql.org/docs/devel/static/release-9-3-4.html
once guaibasaurus does its next buildfarm run a few minutes from
now. Any suggestions?
regards, tom lane
--
Sent via pgsql-hackers mailing li
On 03/15/2014 08:40 PM, Fujii Masao wrote:
Hi,
I executed the following statements in HEAD and 9.3, and compared
the size of WAL which were generated by data insertion in GIN index.
-
CREATE EXTENSION pg_trgm;
CREATE TABLE hoge (col1 text);
CREATE INDEX hogeidx ON hoge USING
Hi,
I executed the following statements in HEAD and 9.3, and compared
the size of WAL which were generated by data insertion in GIN index.
-
CREATE EXTENSION pg_trgm;
CREATE TABLE hoge (col1 text);
CREATE INDEX hogeidx ON hoge USING gin (col1 gin_trgm_ops) WITH
(FASTUPDATE = o
On Fri, Mar 14, 2014 at 7:32 PM, Kyotaro HORIGUCHI
wrote:
> Hello, we found that postgreql won't complete archive recovery
> foever on some situation. This occurs HEAD, 9.3.3, 9.2.7, 9.1.12.
>
> Restarting server with archive recovery fails as following just
> after it was killed with SIGKILL afte
On 15.3.2014 06:40, Peter Geoghegan wrote:
> On Fri, Mar 14, 2014 at 6:44 PM, Tomas Vondra wrote:
>> Well, depends on how you define useful. With the sample dataset
>> 'delicious' (see Peter's post) I can do this:
>>
>>SELECT doc FROM delicious
>> WHERE doc @> '{"title_detail" : {"va
I want to fined when is used these functions(what query caused the call of
these functions) :
-char_bpchar()
-bpchar_name()
-name_bpchar()
On Sat, Mar 15, 2014 at 1:44 AM, Tomas Vondra wrote:
> Because otherwise I don't understand how the index could be used for
> queries with @> '{"a" : {"b" : "c"}}' conditions (i.e. path "[a,b]" with
> value "c").
Hm, some experimentation here shows it does indeed work for queries
like this and w
2014-03-15 19:04 GMT+09:00 Fabien COELHO :
>
> Nice drawing!
>
>
> * How about setting the variable as a float instead of integer? Would
>>>
seem more natural to me. At least as an option.
>>>
>>> Which variable? The values set by setrandom are mostly used for primary
>>> keys. We real
Nice drawing!
* How about setting the variable as a float instead of integer? Would
seem more natural to me. At least as an option.
Which variable? The values set by setrandom are mostly used for primary
keys. We really want integers in a range.
I think he said threshold parameter. Thresh
On Thu, Mar 13, 2014 at 8:06 PM, Amit Kapila wrote:
> On Thu, Mar 13, 2014 at 7:10 PM, Robert Haas wrote:
>> On Thu, Mar 13, 2014 at 12:45 AM, Amit Kapila
>> wrote:
>>> _bt_doinsert - "insert index tuple (X,Y)" (here it will refer to index tuple
>>> location)
>>
>> I don't think that giving the
Oh, sorry, I forgot to write URL referring picture.
http://en.wikipedia.org/wiki/Normal_distribution
http://en.wikipedia.org/wiki/Exponential_distribution
regards,
--
Mitsumasa KONDO
2014-03-15 17:50 GMT+09:00 Mitsumasa KONDO :
> Hi
>
> 2014-03-15 15:53 GMT+09:00 Fabien COELHO :
>
>
>> Hello H
19 matches
Mail list logo
