On Fri, Nov 15, 2013 at 12:34 AM, Heikki Linnakangas <
hlinnakan...@vmware.com> wrote:
> On 14.11.2013 19:26, Alexander Korotkov wrote:
>
>> On Sun, Jun 30, 2013 at 3:00 PM, Heikki Linnakangas <
>> hlinnakan...@vmware.com
>>
>>> wrote:
>>>
>>
>> On 28.06.2013 22:31, Alexander Korotkov wrote:
>>>
Hello, As I mentioned on another thread, I'll reorganize patches
including this and repost them.
Please wait for a while.
--
Kyotaro Horiguchi
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www
Hello, I might made insufficient explanation. Surely it is
overdone for the example.
>> uniquetest=# create table t (a int, b int, c int, d text);
>> uniquetest=# create unique index i_t_pkey on t(a, b);
>> uniquetest=# insert into t
>> (select a % 10, a / 10, a, 't' from generate_series(0, 10
On Fri, Nov 15, 2013 at 12:50 AM, Etsuro Fujita wrote:
>
> I think that, as a secondary effect of the patch, the scan would be
> performed a bit efficiently.
>
>
Hi Etsuro,
Would you be able to supply some benchmarks of a work load which benefits
from this change?
Something which compares patche
On Fri, Nov 15, 2013 at 3:25 AM, Rod Taylor wrote:
> I checked out master and put together a test case using a small percentage
> of production data for a known problem we have with Pg 9.2 and text search
> scans.
>
> A small percentage in this case means 10 million records randomly
> selected; ha
On Thu, Nov 14, 2013 at 3:00 PM, Alexander Korotkov wrote:
> On Thu, Nov 14, 2013 at 2:17 PM, Alexander Korotkov
> wrote:
>
>> On Tue, Nov 5, 2013 at 9:49 PM, Heikki Linnakangas <
>> hlinnakan...@vmware.com> wrote:
>>
>>> On 04.11.2013 23:44, Alexander Korotkov wrote:
>>>
On Mon, Oct 21, 201
> I took a quick look. Observations:
>
> + /* Making query ID dependent on PG version */
> + query->queryId |= PG_VERSION_NUM << 16;
>
> If you want to do something like this, make the value of
> PGSS_FILE_HEADER incorporate (PG_VERSION_NUM / 100) or something.
>
> Why are you doing this?
The thou
On Fri, Nov 15, 2013 at 3:23 AM, Tom Lane wrote:
> Andres Freund writes:
> > I think it'd be a better idea to integrate the sequence caching logic
> > into the relcache. There's a comment about it:
> > * (We can't
> > * rely on the relcache, since it's only, well, a cache, and may decide
> to
+1
interesting feature
Pavel
2013/11/15 Peter Eisentraut
> Various places in the constraint checking code say something like, if we
> ever implement assertions, here is where it should go. I've been
> fiddling with filling in those gaps for some time now, and the other day
> I noticed, hey,
On Fri, Nov 15, 2013 at 3:03 AM, Heikki Linnakangas wrote
>
> I think that means that we should just completely replace the list with
> the hash table. The difference with a small N is lost in noise, so there's
> no point in keeping the list as a fast path for small N. That'll make the
> patch som
On 15 November 2013 10:00 Amit Kapila wrote:
> On Wed, Nov 13, 2013 at 12:02 PM, Haribabu kommi
> wrote:
> > On 12 November 2013 08:47 Amit Kapila wrote:
> >> On Mon, Nov 11, 2013 at 3:14 PM, Haribabu kommi
> >> wrote:
> >> > On 08 November 2013 18:35 Amit Kapila wrote:
> >> >> On Fri, Nov 8, 201
On Thu, Nov 14, 2013 at 11:13 PM, KONDO Mitsumasa
wrote:
> Hi Claudio,
>
>
> (2013/11/14 22:53), Claudio Freire wrote:
>>
>> On Thu, Nov 14, 2013 at 9:09 AM, KONDO Mitsumasa
>> wrote:
>>>
>>> I create a patch that is improvement of disk-read and OS file caches. It
>>> can
>>> optimize kernel read
On Thu, Nov 14, 2013 at 7:25 PM, Peter Geoghegan wrote:
> On Tue, Nov 5, 2013 at 5:30 AM, Sameer Thakur wrote:
>> Hello,
>> Please find attached pg_stat_statements-identification-v9.patch.
>
> I took a quick look. Observations:
>
> + /* Making query ID dependent on PG version */
> + q
On Wed, Nov 13, 2013 at 12:02 PM, Haribabu kommi
wrote:
> On 12 November 2013 08:47 Amit Kapila wrote:
>> On Mon, Nov 11, 2013 at 3:14 PM, Haribabu kommi
>> wrote:
>> > On 08 November 2013 18:35 Amit Kapila wrote:
>> >> On Fri, Nov 8, 2013 at 10:56 AM, Haribabu kommi
>> >> wrote:
>> >> > On 07 N
(2013/11/15 2:09), Fujii Masao wrote:
Agreed.
Could you tell me your agreed reason? I am sorry that I suspect you doesn't
understand this disccusion enough:-(
Regards,
--
Mitsumasa KONDO
NTT Open Source Software Ceter
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To m
(2013/11/15 11:31), Peter Geoghegan wrote:
On Thu, Nov 14, 2013 at 6:28 PM, KONDO Mitsumasa
wrote:
It is confirmation just to make sure, does "this patch" mean my patch? I
agree with you about not adding another lock implementation. It will becomes
overhead.
Yes, I referred to your patch. I d
On Tue, Nov 5, 2013 at 5:30 AM, Sameer Thakur wrote:
> Hello,
> Please find attached pg_stat_statements-identification-v9.patch.
I took a quick look. Observations:
+ /* Making query ID dependent on PG version */
+ query->queryId |= PG_VERSION_NUM << 16;
If you want to do something l
On 15 Listopad 2013, 1:00, David Rowley wrote:
> On Fri, Nov 15, 2013 at 12:33 PM, Tomas Vondra wrote:
>
>> > It is likely far better explained here -->
>> > http://www.courtesan.com/todd/papers/strlcpy.html
>> >
>> > For example , the following 2 lines in jsonfuncs.c
>> >
>> > memset(name, 0, NAM
On Fri, Nov 15, 2013 at 12:00 PM, Peter Eisentraut wrote:
> I'm proposing that we upgrade our Autoconf to 2.69, which is the latest
> right now (release date 2012-04-24). There are no changes in the source
> needed, just tweak the version number in configure.in (see below) and
> run autoreconf.
I'm proposing that we upgrade our Autoconf to 2.69, which is the latest
right now (release date 2012-04-24). There are no changes in the source
needed, just tweak the version number in configure.in (see below) and
run autoreconf. I've compared the configure output before and after on
a few boxes,
On Thu, Nov 14, 2013 at 3:53 PM, Michael Paquier
wrote:
> On Thu, Nov 14, 2013 at 3:02 PM, Sawada Masahiko
> wrote:
>> I attached patch adds new wal_level 'all'.
>> If wal_level is set 'all', the server logs WAL not only when wal_level
>> is set 'hot_standby' ,but also when updating hint bit.
>>
Hi all,
Currently, bgworkers offer the possibility to connect to a given
database using BackgroundWorkerInitializeConnection in bgworker.h, but
there is actually no way to disconnect from a given database inside
the same bgworker process.
One of the use cases for that would be the possibility to
Updated patch attached.
On Sat, 2013-11-09 at 12:09 +0530, Amit Khandekar wrote:
> > > 2) I found the following check a bit confusing, maybe you can make
> it
> > > better
> > > if (!argmodes || argmodes[i] == PROARGMODE_IN || argmodes[i] ==
> > > PROARGMODE_INOUT || argmodes[i] == PROARGMODE_VARI
On Thu, Nov 14, 2013 at 6:28 PM, KONDO Mitsumasa
wrote:
> It is confirmation just to make sure, does "this patch" mean my patch? I
> agree with you about not adding another lock implementation. It will becomes
> overhead.
Yes, I referred to your patch. I don't want to go down this road,
because a
(2013/11/15 11:17), Peter Geoghegan wrote:
On Thu, Nov 14, 2013 at 6:18 PM, KONDO Mitsumasa
wrote:
I will fix it. Could you tell me your Mac OS version and gcc version? I have
only mac book air with Maverick OS(10.9).
I have an idea that Mac OSX doesn't have posix_fadvise at all. Didn't
you u
On Thu, Nov 14, 2013 at 9:09 AM, Fujii Masao wrote:
>> I think that pg_stat_statements should be made to do this kind of
>> thing by a third party tool that aggregates snapshots of deltas.
>> Time-series data, including (approximate) *local* minima and maxima
>> should be built from that. I think
(2013/11/14 7:11), Peter Geoghegan wrote:
On Wed, Oct 23, 2013 at 8:52 PM, Alvaro Herrera
wrote:
Hmm, now if we had portable atomic addition, so that we could spare the
spinlock ...
And adding a histogram or
min/max for something like execution time isn't an approach that can
be made to work f
On Thu, Nov 14, 2013 at 6:18 PM, KONDO Mitsumasa
wrote:
> I will fix it. Could you tell me your Mac OS version and gcc version? I have
> only mac book air with Maverick OS(10.9).
I have an idea that Mac OSX doesn't have posix_fadvise at all. Didn't
you use the relevant macros so that the code at
(2013/11/15 2:03), Fujii Masao wrote:
On Thu, Nov 14, 2013 at 9:09 PM, KONDO Mitsumasa
wrote:
Hi,
I create a patch that is improvement of disk-read and OS file caches. It can
optimize kernel readahead parameter using buffer access strategy and
posix_fadvice() in various disk-read situations.
Hi Claudio,
(2013/11/14 22:53), Claudio Freire wrote:
On Thu, Nov 14, 2013 at 9:09 AM, KONDO Mitsumasa
wrote:
I create a patch that is improvement of disk-read and OS file caches. It can
optimize kernel readahead parameter using buffer access strategy and
posix_fadvice() in various disk-read s
On Thu, Nov 14, 2013 at 04:58:55PM -0800, Peter Geoghegan wrote:
> On Thu, Nov 14, 2013 at 4:53 PM, Adrian Klaver
> wrote:
> > Is a review necessary at this point?
>
> No. Just mark it committed.
Oh, sorry, I didn't realize it was in the commit-fest app.
--
Bruce Momjian http://mom
On Fri, Nov 15, 2013 at 3:12 AM, Andres Freund wrote:
> Hi,
>
> On 2013-11-13 22:55:43 +1300, David Rowley wrote:
> > Here
> > http://www.postgresql.org/message-id/24278.1352922...@sss.pgh.pa.usthere
> > was some talk about init_sequence being a bottleneck when many sequences
> > are used in a si
On Thu, Nov 14, 2013 at 4:53 PM, Adrian Klaver wrote:
> Is a review necessary at this point?
No. Just mark it committed.
--
Peter Geoghegan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ha
Initial review of the patch submitted in this message and listed in the
current CommitFest:
http://www.postgresql.org/message-id/cagpqqf3xwwc_4fhinz_g6ecvps_ov3k2pe4-aj1dg4iyy+f...@mail.gmail.com
This patch would seem to be already committed here
http://git.postgresql.org/gitweb/?p=postgresql.
On Fri, Nov 15, 2013 at 12:33 PM, Tomas Vondra wrote:
> > It is likely far better explained here -->
> > http://www.courtesan.com/todd/papers/strlcpy.html
> >
> > For example , the following 2 lines in jsonfuncs.c
> >
> > memset(name, 0, NAMEDATALEN);
> > strncpy(name, fname, NAMEDATALEN);
>
> Be
On 15 Listopad 2013, 0:07, David Rowley wrote:
> Hi All,
>
> As a bit of a background task, over the past few days I've been analysing
> the uses of strncpy in the code just to try and validate if it is the
> right
> function to be using. I've already seen quite a few places where their
> usage is
On Fri, Nov 15, 2013 at 3:03 AM, Heikki Linnakangas wrote:
> On 14.11.2013 14:38, David Rowley wrote:
>
>> I've just completed some more benchmarking of this. I didn't try dropping
>> the threshold down to 2 or 0 but I did tests at the cut over point and
>> really don't see much difference in per
On Thu, Nov 14, 2013 at 3:08 PM, Tom Lane wrote:
> I'm a bit inclined to take the risk of breaking anything that's calling
> get_eclass_for_sort_expr() directly. Thoughts?
It's worth being aware of the fact that Peter E's Jenkins instance
seems to track regressions for some popular third party e
Attached patch changes the default ciphersuite to
HIGH:!aNULL
instead of old
DEFAULT:!LOW:!EXP:!MD5:@STRENGTH
where DEFAULT is a shortcut for "ALL:!aNULL:!eNULL".
Main goal is to leave low-level ciphersuite details to OpenSSL guys
and give clear impression to Postgres admins what it i
I looked into bug #8591:
http://www.postgresql.org/message-id/e1vgk41-00050x...@wrigleys.postgresql.org
and was able to reproduce the problem. The proximate cause is that
get_eclass_for_sort_expr is wrong to suppose that it can always create new
equivalence class entries with empty em_nullable_rel
Hi All,
As a bit of a background task, over the past few days I've been analysing
the uses of strncpy in the code just to try and validate if it is the right
function to be using. I've already seen quite a few places where their
usage is wrongly assumed.
As many of you will know and maybe some of
Pavel Stehule writes:
> one my customer reported a "out of memory" issue. After investigation he
> found a main problem in large query that uses a lot of union all queries.
> He wrote a self test:
> do $$
> declare i integer; str text='';
> begin
> for i in 1..1000 loop
> str := str || 'unio
Hello,
one my customer reported a "out of memory" issue. After investigation he
found a main problem in large query that uses a lot of union all queries.
He wrote a self test:
do $$
declare i integer; str text='';
begin
for i in 1..1000 loop
str := str || 'union all select i,i,i from generat
On Thu, Nov 14, 2013 at 5:41 AM, Sameer Thakur wrote:
> So i think -g option is failing
Right you are.
I was missing a "g:" in the getopt_long() call.
Attached is a revised patch that handles that.
And it behaves better:
postgres@cbbrowne ~/p/s/b/scripts> ./createuser -g purge_role -U
postgres
rebased patch
Regards
Pavel
2013/11/14 Peter Eisentraut
> On Wed, 2013-10-09 at 18:57 +0200, Pavel Stehule wrote:
> > here is a patch for RAISE WHEN clause
>
> Your patch needs to be rebased.
>
>
diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index ca2c2b5..d6845d7 100644
I wrote:
> Robert Haas writes:
>> I'm not volunteering to spend time fixing this, but I disagree with
>> the premise that it isn't worth fixing, because I think it's a POLA
>> violation.
> Yeah, I'm not terribly comfortable with letting it go either. Attached
> is a proposed patch. I couldn't s
Bruce Momjian writes:
>> • is used to separate names in a path
>> • * is used to match any name in a path
>> • > is used to recursively match any destination starting from this name
>>
>> For example using the example above, these subscriptions are possible
>>
>> Subscription
On 14.11.2013 19:26, Alexander Korotkov wrote:
On Sun, Jun 30, 2013 at 3:00 PM, Heikki Linnakangas
wrote:
On 28.06.2013 22:31, Alexander Korotkov wrote:
Now, I got the point of three state consistent: we can keep only one
consistent in opclasses that support new interface. exact true and ex
Hannu Krosing-5 wrote
> On 11/14/2013 08:17 PM, Merlin Moncure wrote:
>> On Thu, Nov 14, 2013 at 11:34 AM, David E. Wheeler
>> <
> david@
> > wrote:
>>> On Nov 14, 2013, at 7:07 AM, Merlin Moncure <
> mmoncure@
> > wrote:
>>>
This is exactly what needs to be done, full stop (how about: hst
On 11/14/2013 08:17 PM, Merlin Moncure wrote:
> On Thu, Nov 14, 2013 at 11:34 AM, David E. Wheeler
> wrote:
>> On Nov 14, 2013, at 7:07 AM, Merlin Moncure wrote:
>>
>>> This is exactly what needs to be done, full stop (how about: hstore).
>>> It really comes down to this: changing the serializati
Zhan Li writes:
> Thank you for your reply Tom. Then a) what are exactly stored in the
> pathlist of top level rel? Paths worth considering? b) I have been
> struggling to come up with a way to print the Path struct. If I can print a
> path the way like "A hash join (B nested loop join C)", that w
On Thu, Nov 14, 2013 at 11:34 AM, David E. Wheeler
wrote:
> On Nov 14, 2013, at 7:07 AM, Merlin Moncure wrote:
>
>> This is exactly what needs to be done, full stop (how about: hstore).
>> It really comes down to this: changing the serialization behaviors
>> that have been in production for 2 rel
On Fri, Oct 25, 2013 at 02:58:12PM -0400, Andrew Dunstan wrote:
>
> On 10/25/2013 01:50 PM, Emanuel Calvo wrote:
> >
> >Hi guys,
> >
> >I'm working on a quick convertion script for query reviews and I
> >wonder if a feature request to add the following values will be
> >possible:
> >
> > %D = dura
On Thu, Nov 14, 2013 at 12:29:58PM -0500, Rayson Ho wrote:
> http://aws.typepad.com/aws/2013/11/amazon-rds-for-postgresql-now-available.html
>
> (The "Free Tier" page has not been updated yet, but I believe
> PostgreSQL should also be free for new AWS users:
> http://aws.amazon.com/free/ )
Here i
On Thu, Oct 24, 2013 at 11:41:57AM -0400, Sev Zaslavsky wrote:
> Here is an example implementation: http://activemq.apache.org/nms/
> activemq-wildcards.html
>
>
> • is used to separate names in a path
> • * is used to match any name in a path
> • > is used to recursively match any destinat
On Thu, Nov 14, 2013 at 9:08 PM, Haribabu kommi
wrote:
> Please find attached the patch, for adding a new option for pg_basebackup,
> to specify a different directory for pg_xlog.
Sounds good! Here are the review comments:
+printf(_("--xlogdir=XLOGDIR location for the
transaction l
On Nov 14, 2013, at 7:07 AM, Merlin Moncure wrote:
> This is exactly what needs to be done, full stop (how about: hstore).
> It really comes down to this: changing the serialization behaviors
> that have been in production for 2 releases (three if you count the
> extension) is bad enough, but mak
http://aws.typepad.com/aws/2013/11/amazon-rds-for-postgresql-now-available.html
(The "Free Tier" page has not been updated yet, but I believe
PostgreSQL should also be free for new AWS users:
http://aws.amazon.com/free/ )
Rayson
==
Open Grid Schedu
On Thu, Nov 14, 2013 at 10:54 AM, Hannu Krosing wrote:
> On 11/14/2013 05:06 PM, Merlin Moncure wrote:
>> On Thu, Nov 14, 2013 at 9:42 AM, Hannu Krosing wrote:
>>> This is supported by the fact that current functions on json-source
>>> treat it as json-object (for example key lookup gives you the
On Sun, Jun 30, 2013 at 3:00 PM, Heikki Linnakangas wrote:
> On 28.06.2013 22:31, Alexander Korotkov wrote:
>
>> Now, I got the point of three state consistent: we can keep only one
>> consistent in opclasses that support new interface. exact true and exact
>> false values will be passed in the c
Thank you for your reply Tom. Then a) what are exactly stored in the
pathlist of top level rel? Paths worth considering? b) I have been
struggling to come up with a way to print the Path struct. If I can print a
path the way like "A hash join (B nested loop join C)", that would be
great. You mentio
On Thu, Nov 14, 2013 at 7:11 AM, Peter Geoghegan wrote:
> On Wed, Oct 23, 2013 at 8:52 PM, Alvaro Herrera
> wrote:
>> Hmm, now if we had portable atomic addition, so that we could spare the
>> spinlock ...
>
> That certainly seems like an interesting possibility.
>
> I think that pg_stat_statemen
On Thu, Nov 14, 2013 at 9:09 PM, KONDO Mitsumasa
wrote:
> Hi,
>
> I create a patch that is improvement of disk-read and OS file caches. It can
> optimize kernel readahead parameter using buffer access strategy and
> posix_fadvice() in various disk-read situations.
When I compiled the HEAD code wi
Zhan Li writes:
> When searching all the possible paths of executing a query, the optimizer
> finds and saves the cheapest paths for the top level rel. I'd like to check
> out all the paths the optimizer has ever considered, which I believe, are
> stored in the pathlist of the top level rel.
No,
On 11/14/2013 05:06 PM, Merlin Moncure wrote:
> On Thu, Nov 14, 2013 at 9:42 AM, Hannu Krosing wrote:
>> This is supported by the fact that current functions on json-source
>> treat it as json-object (for example key lookup gives you the value
>> of latest key and not a list of all matching key va
On 11/14/2013 01:47 PM, Andrew Dunstan wrote:
>
> On 11/14/2013 03:21 AM, Hannu Krosing wrote:
>> On 11/14/2013 01:32 AM, David E. Wheeler wrote:
>>> On Nov 13, 2013, at 3:59 PM, Hannu Krosing
>>> wrote:
>>>
I remember strong voices in support of *not* normalising json, so that
things li
On 11/14/2013 04:07 PM, Merlin Moncure wrote:
> On Wed, Nov 13, 2013 at 6:01 PM, Hannu Krosing wrote:
>>
>> I guess we should not replace current JSON type with hstore based
>> one, but add something json-like based on nested hstore instead.
>>
>> Maybe call it jsdoc or jdoc or jsobj or somesuch.
When searching all the possible paths of executing a query, the optimizer
finds and saves the cheapest paths for the top level rel. I'd like to check
out all the paths the optimizer has ever considered, which I believe, are
stored in the pathlist of the top level rel. But I do not have an idea of
h
On Thu, Nov 14, 2013 at 9:42 AM, Hannu Krosing wrote:
> This is supported by the fact that current functions on json-source
> treat it as json-object (for example key lookup gives you the value
> of latest key and not a list of all matching key values).
yeah. hm. that's a good point.
Maybe there
On 11/14/2013 12:20 AM, Josh Berkus wrote:
> Merlin,
>
>
>> I use pg/JSON all over the place. In several cases I have to create
>> documents with ordered keys because the parser on the other side wants
>> them that way -- this is not a hypothetical argument. The current
>> json serialization API
On 11/14/2013 01:42 AM, Andrew Dunstan wrote:
>
> On 11/13/2013 07:01 PM, Hannu Krosing wrote:
>>
>> I guess we should not replace current JSON type with hstore based
>> one, but add something json-like based on nested hstore instead.
>
>
> Well, that's two voices for that course of action.
I am no
Andres Freund writes:
> On 2013-11-14 09:52:11 -0500, Tom Lane wrote:
>> In HEAD:
>>
>> regression=# \d tenk1_thous_tenthous
>> ERROR: column i.indisidentity does not exist
>> LINE 4: i.indisidentity,
>> ^
> That's me. At some point indisidentity was renamed to indisreplident.
> Patch attached
On 2013-11-14 09:52:11 -0500, Tom Lane wrote:
> In HEAD:
>
> regression=# \d tenk1_thous_tenthous
> ERROR: column i.indisidentity does not exist
> LINE 4: i.indisidentity,
> ^
That's me. At some point indisidentity was renamed to indisreplident.
Patch attached (also renaming a variable
On Wed, Nov 13, 2013 at 6:01 PM, Hannu Krosing wrote:
> On 11/14/2013 12:09 AM, Merlin Moncure wrote:
>> On Wed, Nov 13, 2013 at 4:16 PM, Josh Berkus wrote:
>>> On 11/13/2013 06:45 AM, Merlin Moncure wrote:> I'm not so sure we should
>>> require hstore to do things like build
Also, json_obje
In HEAD:
regression=# \d tenk1_thous_tenthous
ERROR: column i.indisidentity does not exist
LINE 4: i.indisidentity,
^
This works fine in released versions.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On 2013-11-14 09:47:18 -0500, Tom Lane wrote:
> Andres Freund writes:
> > On 2013-11-14 09:23:20 -0500, Tom Lane wrote:
> >> We most certainly *do* discard entries, if they're not open when a cache
> >> flush event comes along.
>
> > What I was aiming at is that we don't discard them because of a
On Tue, Nov 12, 2013 at 10:22:20PM -0500, Peter Eisentraut wrote:
> Similar to recent pg_upgrade changes
> (https://commitfest.postgresql.org/action/patch_view?id=1216), here is a
> patch to separate the terminating and nonterminating variants of
> mmerror() in ecpg.
> ...
Haven't tried it, but it
Andres Freund writes:
> On 2013-11-14 09:23:20 -0500, Tom Lane wrote:
>> We most certainly *do* discard entries, if they're not open when a cache
>> flush event comes along.
> What I was aiming at is that we don't discard them because of a limited
> cache size. I don't think it means much that we
On Wed, Nov 13, 2013 at 04:50:49PM -0800, David E. Wheeler wrote:
> On Nov 13, 2013, at 4:45 PM, Andrew Dunstan wrote:
>
> >> It should be a pretty-printing function option, perhaps, but not core to
> >> the type itself, IMO.
> >
> > I don't in the least understand how it could be a pretty prin
Magnus Hagander writes:
> That code was originally "stolen" from psql, and then whacked around a
> number of times. The part about looping and passwords, for example, is in
> startup.c in psql as well. We probably want to fix it there as well (even
> if it doesn't have the same problem, it has th
On 2013-11-14 09:23:20 -0500, Tom Lane wrote:
> Andres Freund writes:
> > I think it'd be a better idea to integrate the sequence caching logic
> > into the relcache. There's a comment about it:
> > * (We can't
> > * rely on the relcache, since it's only, well, a cache, and may decide to
> > *
Andres Freund writes:
> I think it'd be a better idea to integrate the sequence caching logic
> into the relcache. There's a comment about it:
> * (We can't
> * rely on the relcache, since it's only, well, a cache, and may decide to
> * discard entries.)
> but that's not really accurate anymore
Hi,
On 2013-11-13 22:55:43 +1300, David Rowley wrote:
> Here http://www.postgresql.org/message-id/24278.1352922...@sss.pgh.pa.us there
> was some talk about init_sequence being a bottleneck when many sequences
> are used in a single backend.
>
> The attached I think implements what was talked abo
On 14.11.2013 14:38, David Rowley wrote:
I've just completed some more benchmarking of this. I didn't try dropping
the threshold down to 2 or 0 but I did tests at the cut over point and
really don't see much difference in performance between the list at 32 and
the hashtable at 33 sequences. The h
On Thu, Nov 14, 2013 at 9:09 AM, KONDO Mitsumasa
wrote:
> I create a patch that is improvement of disk-read and OS file caches. It can
> optimize kernel readahead parameter using buffer access strategy and
> posix_fadvice() in various disk-read situations.
>
> In general OS, readahead parameter wa
On 11/14/2013 03:21 AM, Hannu Krosing wrote:
On 11/14/2013 01:32 AM, David E. Wheeler wrote:
On Nov 13, 2013, at 3:59 PM, Hannu Krosing wrote:
I remember strong voices in support of *not* normalising json, so that
things like
{"a":1,"a":true, "a":"b", "a":none}
would go through the system
Oh! Sorry...
I forgot to attach my latest patch.
Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center
diff --git a/contrib/pg_stat_statements/pg_stat_statements--1.1--1.2.sql b/contrib/pg_stat_statements/pg_stat_statements--1.1--1.2.sql
new file mode 100644
index 000..929d623
--- /dev/n
(2013/10/21 20:17), KONDO Mitsumasa wrote:
> (2013/10/18 22:21), Andrew Dunstan wrote:
>> If we're going to extend pg_stat_statements, even more than min and max
>> I'd like to see the standard deviation in execution time.
> OK. I do! I am making some other patches, please wait more!
I add stddev_t
Please find attached the patch, for adding a new option for pg_basebackup, to
specify a different directory for pg_xlog.
Design
A new option: "xlogdir" is added to the list of options for pg_basebackup. The
new option is not having an equivalent short option letter.
This option will allow the
I'd like to do the complementary explanation of this.
In tbm_union_page() and tbm_intersect_page() in tidbitmap.c, WORDS_PER_PAGE
is used in the scan of a lossy chunk, instead of WORDS_PER_CHUNK, where
these macros are defined as:
/* number of active words for an exact page: */
#define WORDS_PER_
On Thu, Nov 14, 2013 at 2:17 PM, Alexander Korotkov wrote:
> On Tue, Nov 5, 2013 at 9:49 PM, Heikki Linnakangas <
> hlinnakan...@vmware.com> wrote:
>
>> On 04.11.2013 23:44, Alexander Korotkov wrote:
>>
>>> On Mon, Oct 21, 2013 at 11:12 PM, Alexander Korotkov
>>> wrote:
>>>
>>> Attached version o
> 1. cloned from https://github.com/samthakur74/postgres
Sorry. cloned from https://github.com/postgres/postgres
regards
Sameer
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hello,
> When I read it again and try to relate, I get your point. Actually true,
> hashes must always be performed as last option (if that is what you too
> meant) and if there are few other operations they must be the last one to
> be performed especially after sorting/grouping. Hashes must some
On 11/14/2013 07:02 AM, Sawada Masahiko wrote:
I attached patch adds new wal_level 'all'.
Shouldn't this be a separate setting? It's useful for storage which
requires rewriting a partially written sector before it can be read again.
--
Florian Weimer / Red Hat Product Security Team
--
Se
On Thursday, November 7, 2013, Marko Kreen wrote:
> On Wed, Nov 06, 2013 at 09:57:32PM -0300, Alvaro Herrera wrote:
> > Marko Kreen escribió:
> >
> > > By default OpenSSL (and SSL/TLS in general) lets client cipher
> > > order take priority. This is OK for browsers where the ciphers
> > > were tu
On Wednesday, November 13, 2013, Tom Lane wrote:
> Kevin Grittner > writes:
> > If nobody objects, I'll fix that small memory leak in the
> > regression test driver. Hopefully someone more familiar with
> > pg_basebackup will fix the double-free (and related problems
> > mentioned by Tom) in stre
Hello,
Tried to test this patch. Did the following
1. cloned from https://github.com/samthakur74/postgres
2. Applied patch and make install
3. created rolesapp_readonly_role,app2_writer_role
4. Tried createuser -D -S -l -g app_readonly_role,app2_writer_role
test_user got error: createuser: invalid
On 11/14/13 10:27 AM, Mika Eloranta wrote:
On 13 Nov 2013, at 20:51, Mika Eloranta wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
Same patch as an attachment.
I can't comment on the usefulness of this patch, but the first hunk in
pro
On 11/14/13 7:08 AM, Tatsuo Ishii wrote:
It means "the connection is idle except for keepalive packets".
We could perhaps just drop the word "otherwise", if people find
it confusing.
Wah. I seemed to completely misunderstand what the pharase
says. Thanks for clarification. I agree to drop "othe
On Tue, Nov 5, 2013 at 9:49 PM, Heikki Linnakangas
wrote:
> On 04.11.2013 23:44, Alexander Korotkov wrote:
>
>> On Mon, Oct 21, 2013 at 11:12 PM, Alexander Korotkov
>> wrote:
>>
>> Attached version of patch is debugged. I would like to note that number
>>> of
>>> bugs was low and it wasn't very h
1 - 100 of 104 matches
Mail list logo