On Tue, May 15, 2018 at 11:43 AM, David Rowley
wrote:
> On 12 May 2018 at 03:08, Bruce Momjian wrote:
>> I have committed the first draft of the Postgres 11 release notes. I
>> will add more markup soon. You can view the most current version here:
>>
>> http://momjian.us/pgsql_docs/rele
Hi,
I noticed that if log_min_messages is set to ‘debug2’, it shows ‘debug’ instead
of debug2.
Showing other debug options like debug1 work normally.
This is same for client_min_messages.
According to a033daf56 and baaad2330, debug is an alias for debug2 and for
backward-compatibility.
And also
> On 30 March 2018 at 14:53, Konstantin Knizhnik
wrote:
> Hi hackers,
> One of our customers was managed to improve speed about 10 times by using
SSL compression for the system where client and servers are located in
different geographical regions
> and query results are very large because of JSON
Hi,
Is anybody still working on this? Are there any plans to add this to
commitfest?
I'd like to add planning time to auto_explain, and it turns out that
this patch is somewhat relevant to that feature.
The current approach here is to set planning_time in PlannedStmt via
planner_hook, whic
This gets further refactoring.
At Fri, 11 May 2018 17:45:20 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
wrote in
<20180511.174520.188681124.horiguchi.kyot...@lab.ntt.co.jp>
> But, this is not just a rebased version. On the way fixing
> serious conflicts, I refactored patch and I believe this
On 15.05.2018 13:23, Dmitry Dolgov wrote:
> On 30 March 2018 at 14:53, Konstantin Knizhnik
mailto:k.knizh...@postgrespro.ru>> wrote:
> Hi hackers,
> One of our customers was managed to improve speed about 10 times by
using SSL compression for the system where client and servers are
located i
On Mon, May 14, 2018 at 7:20 AM, Stas Kelvich wrote:
> Summarising, I think, that introducing some permanent connections to
> postgres_fdw node will put too much burden on this patch set and that it will
> be possible to address that later (in a long run such connection will be
> anyway
> needed
On 05/15/2018 08:53 AM, Konstantin Knizhnik wrote:
On 15.05.2018 13:23, Dmitry Dolgov wrote:
> On 30 March 2018 at 14:53, Konstantin Knizhnik
mailto:k.knizh...@postgrespro.ru>> wrote:
> Hi hackers,
> One of our customers was managed to improve speed about 10 times by
using SSL compression
On 15 May 2018 at 21:36, Andrew Dunstan
wrote:
>
>
>>> > To use zstd compression, Postgres should be configured with
>>> --with-zstd. Otherwise compression will use zlib unless it is disabled by
>>> --without-zlib option.
>>> > I have added compression=on/off parameter to connection string and -Z
David Rowley writes:
> On 15 May 2018 at 08:28, Bruce Momjian wrote:
>> Consistently return NaN for
>> NaN inputs to power()
>> on older platforms (Dang Minh Huong)
> While I'm not in favour of removing Dang's credit here, technically
> this patch was Tom's. The code added in float.c by Dang's p
Andrew Dunstan wrote:
> I'm not necessarily opposed to this, but I'm not certain about the use
> case either.
+1.
The downside is that it would create the need, when using COPY TO,
to know whether an input file was generated with or without header,
and a hazard on mistakes.
If you say it
2018-05-15 9:53 GMT-03:00 Konstantin Knizhnik :
> Looks like community is not so interested in this patch. Frankly speaking I
> do not understand why.
>
AFAICS the lack of replies is due to feature freeze. I'm pretty sure
people are interested in this topic (at least I am). Did you review a
previou
Hi hackers!
Experimenting with the new pluggable storage API, I found that amcanbackward
flag is not checked in build_index_paths() before
build_index_pathkeys(... BackwardScanDirection) call when we are building
paths for ORDER BY. And this flag is even not copied into IndexOptInfo struct.
Obvi
Hackers,
There was a bug report sent by Hao Lee about Windows build breakage,
"BUG #15167: error C2365: 'errcode' : redefinition; previous definition"
https://www.postgresql.org/message-id/152446498404.19807.4659286570762153837%40wrigleys.postgresql.org
Heikki was the only person who responded to
On 15 May 2018 at 10:26, Daniel Verite wrote:
> Andrew Dunstan wrote:
>
> > I'm not necessarily opposed to this, but I'm not certain about the use
> > case either.
>
> +1.
> The downside is that it would create the need, when using COPY TO,
> to know whether an input file was generated wi
Mark Dilger writes:
> My best guess at the moment is:
> diff --git a/src/backend/utils/init/globals.c
> b/src/backend/utils/init/globals.c
> index c1f0441b08..0a3163398f 100644
> --- a/src/backend/utils/init/globals.c
> +++ b/src/backend/utils/init/globals.c
> @@ -16,8 +16,11 @@
> *
> *-
Isaac Morland writes:
> On 15 May 2018 at 10:26, Daniel Verite wrote:
>> Andrew Dunstan wrote:
>>> I'm not necessarily opposed to this, but I'm not certain about the use
>>> case either.
>> The downside is that it would create the need, when using COPY TO,
>> to know whether an input file was ge
On Tuesday, May 15, 2018, Tom Lane wrote:
>
>
> AFAICS, Daniel's just reacting to the basic idea of a header line.
> I agree that by itself that's not worth much. However, if we added
> your proposed option to insist that the column names match during COPY
> IN, I think that that could have some
> On May 15, 2018, at 8:58 AM, Tom Lane wrote:
>
> Mark Dilger writes:
>> My best guess at the moment is:
>
>> diff --git a/src/backend/utils/init/globals.c
>> b/src/backend/utils/init/globals.c
>> index c1f0441b08..0a3163398f 100644
>> --- a/src/backend/utils/init/globals.c
>> +++ b/src/back
Greetings,
* Mark Dilger (hornschnor...@gmail.com) wrote:
> > On May 15, 2018, at 8:58 AM, Tom Lane wrote:
> > Mark Dilger writes:
> >> My best guess at the moment is:
> >
> >> diff --git a/src/backend/utils/init/globals.c
> >> b/src/backend/utils/init/globals.c
> >> index c1f0441b08..0a316339
> On May 15, 2018, at 9:29 AM, Stephen Frost wrote:
>
> Greetings,
>
> * Mark Dilger (hornschnor...@gmail.com) wrote:
>>> On May 15, 2018, at 8:58 AM, Tom Lane wrote:
>>> Mark Dilger writes:
My best guess at the moment is:
>>>
diff --git a/src/backend/utils/init/globals.c
b/s
Mark Dilger writes:
> I'm curious why the Windows build farm members did not pick this up. Or
> perhaps they did? (I don't get emails about that.)
They did not, and I too was wondering why not.
> If none of the animals
> are configured to detect this bug, perhaps the community needs another
>
> On May 15, 2018, at 9:54 AM, Tom Lane wrote:
>
> Mark Dilger writes:
>> I'm curious why the Windows build farm members did not pick this up. Or
>> perhaps they did? (I don't get emails about that.)
>
> They did not, and I too was wondering why not.
>
>> If none of the animals
>> are confi
Mark Dilger writes:
>>> If none of the animals
>>> are configured to detect this bug, perhaps the community needs another
>>> Windows animal configured along the lines of the build machine I am using?
>> +1. How do you have yours configured, anyway?
> I mostly develop on mac and linux and don't
> On May 15, 2018, at 10:20 AM, Tom Lane wrote:
>
> Mark Dilger writes:
If none of the animals
are configured to detect this bug, perhaps the community needs another
Windows animal configured along the lines of the build machine I am using?
>
>>> +1. How do you have yours confi
Mark Dilger writes:
>> On May 15, 2018, at 10:20 AM, Tom Lane wrote:
>> Hm. I'm not sure what our nominal support range for Visual Studio is.
>> I see that mastodon (running VS2005) and currawong (running VS2008)
>> haven't reported on HEAD lately, and I think they may have been shut
>> down int
On 2018-Apr-23, Alvaro Herrera wrote:
> Now, frankly, this being mostly a debugging tool, I think it would be
> better to have the output as complete as we can. Otherwise, when
> debugging some hideous problem we find ourselves patching the tool
> during an emergency in order to figure out what i
Isaac Morland wrote:
> Just to be clear, we're talking about my "header match" feature, not the
> basic idea of allowing a header in text format?
For my reply it was on merely allowing it, as does the current
patch at https://commitfest.postgresql.org/18/1629
Best regards,
--
Daniel Vér
On 05/15/2018 01:20 PM, Tom Lane wrote:
Mark Dilger writes:
If none of the animals
are configured to detect this bug, perhaps the community needs another
Windows animal configured along the lines of the build machine I am using?
+1. How do you have yours configured, anyway?
I mostly develo
On 2018-05-15 13:44:58 -0400, Alvaro Herrera wrote:
> On 2018-Apr-23, Alvaro Herrera wrote:
>
> > Now, frankly, this being mostly a debugging tool, I think it would be
> > better to have the output as complete as we can. Otherwise, when
> > debugging some hideous problem we find ourselves patchin
On Tue, May 15, 2018 at 08:45:07AM +0530, Amit Kapila wrote:
> No, it is not like that. We divide the scan among workers and each
> worker should perform projection of the rows it scanned (after
> applying filter). Now, if the expensive functions are part of target
> lists, then we can push the c
On Tue, May 15, 2018 at 6:29 PM, Tom Lane wrote:
> Mark Dilger writes:
>
> > I don't have a strong opinion on that. I could also look to upgrade
> > to a newer version. Generally, I try to build using the oldest
> > supported version rather than the newest. What is the next oldest
> > working
On 16 May 2018 at 02:01, Tom Lane wrote:
> David Rowley writes:
>> While I'm not in favour of removing Dang's credit here, technically
>> this patch was Tom's. The code added in float.c by Dang's patch
>> (61b200e2f) was effectively reverted by 6bdf1303. Dang's regression
>> tests remain, so sho
On Tue, May 15, 2018 at 09:51:47AM +0900, Tatsuo Ishii wrote:
> >> I could not find this:
> >>
> >> $ git log -1 f8e5f15
> >> commit f8e5f156b30efee5d0038b03e38735773abcb7ed
> >> Author: Andres Freund
> >> Date: Mon Sep 18 19:36:44 2017 -0700
> >>
> >> Rearm statement_timeout after each ex
Hi!
I'm not understand why postgres prefers to sort table instead of using
index only scan when query is a simple inner join on composite type.
Query with equality clause with constant works fine with index scan but
join not. Could somebody point me why? Thank you.
And I'm not able to force
On Tue, May 15, 2018 at 06:40:18AM +, Huong Dangminh wrote:
> Hi,
>
> > From: David Rowley [mailto:david.row...@2ndquadrant.com]
> > Sent: Tuesday, May 15, 2018 3:01 PM
> > To: Bruce Momjian
> > Cc: Đặng Minh Hướng ; PostgreSQL-development
> >
> > Subject: Re: Postgres 11 release notes
> >
On Tue, May 15, 2018 at 02:26:33PM +0900, Etsuro Fujita wrote:
> (2018/05/12 0:08), Bruce Momjian wrote:
> >I have committed the first draft of the Postgres 11 release notes. I
> >will add more markup soon. You can view the most current version here:
> >
> > http://momjian.us/pgsql_docs/relea
This is for tracking planid into pg_stat_statements too.
A first try is available here
http://www.postgresql-archive.org/Poc-pg-stat-statements-with-planid-td6014027.html
reusing pg_stat_plans's "Plan tree Jumbling algorithm" from Peter Geoghegan.
Hashing the normalized query plan text in one pa
It seems quite strange to me that we calculate total_pages before any
partition pruning and constraint exclusion is performed during
set_base_rel_sizes(). Wouldn't it be better to wait until after that's
done so we don't mistakenly count relations we're not going to scan?
Delaying the calculation
On Tue, May 15, 2018 at 01:04:55PM +0530, Amit Kapila wrote:
> On Tue, May 15, 2018 at 11:43 AM, David Rowley
> wrote:
> > On 12 May 2018 at 03:08, Bruce Momjian wrote:
> >> I have committed the first draft of the Postgres 11 release notes. I
> >> will add more markup soon. You can view the mos
David Rowley writes:
> It seems quite strange to me that we calculate total_pages before any
> partition pruning and constraint exclusion is performed during
> set_base_rel_sizes(). Wouldn't it be better to wait until after that's
> done so we don't mistakenly count relations we're not going to sc
On Tue, May 15, 2018 at 3:45 PM, legrand legrand
wrote:
> Would there be some functional or performances reasons to prefer jumbling to
> hashing normalized plan text?
Using the text could produce different query IDs for the same plan if
any information is displayed in the text format which can va
Teodor Sigaev writes:
> I'm not understand why postgres prefers to sort table instead of using
> index only scan when query is a simple inner join on composite type.
> Query with equality clause with constant works fine with index scan but
> join not. Could somebody point me why? Thank you.
Hm
Robert Haas writes:
> On Tue, May 15, 2018 at 3:45 PM, legrand legrand
> wrote:
>> Would there be some functional or performances reasons to prefer jumbling to
>> hashing normalized plan text?
> Basically, I would be nervous about the idea of an EXPLAIN output
> that's required to reflect all an
On Tue, Mar 27, 2018 at 8:19 AM, Arthur Zakirov
wrote:
>> I assume the DSM infrastructure already has some solution for getting
>> rid of DSM segments when the last interested process disconnects,
>> so maybe you could piggyback on that somehow.
>
> Yes, there is dsm_pin_mapping() for this. But it
>> This commit gives user-visible changes to the statment timeout
>> behavior. So I think this should be added to the release notes.
>
> OK, makes sense. Here is what I added:
>
> 2017-09-18 [f8e5f156b] Rearm statement_timeout after each executed
> query.
>
> In the Extended Query
On Wed, Mar 28, 2018 at 9:56 PM, David G. Johnston
wrote:
> On Wed, Mar 28, 2018 at 6:38 PM, Isaac Morland
> wrote:
>> One question I would have is: what proposals exist or have existed for
>> additional privilege bits? How much pressure is there to use some of the
>> remaining bits? I actually l
Dear hackers,
I’m working on a foreign database wrapper for Kafka [1]
Now I am trying to make it parallel aware. Following
the documentation [2]
However it seems that I can’t make it use more than a
single worker with force_parallel_mode = on.
I wonder if I need to do more than just implementing
> On May 15, 2018, at 12:50 PM, Andres Freund wrote:
>
> On 2018-05-15 13:44:58 -0400, Alvaro Herrera wrote:
>> On 2018-Apr-23, Alvaro Herrera wrote:
>>
>>> Now, frankly, this being mostly a debugging tool, I think it would be
>>> better to have the output as complete as we can. Otherwise, whe
On 2018-05-15 16:28:23 -0500, Jonathan S. Katz wrote:
>
> > On May 15, 2018, at 12:50 PM, Andres Freund wrote:
> >
> > On 2018-05-15 13:44:58 -0400, Alvaro Herrera wrote:
> >> On 2018-Apr-23, Alvaro Herrera wrote:
> >>
> >>> Now, frankly, this being mostly a debugging tool, I think it would be
David Rowley writes:
> On 16 May 2018 at 02:01, Tom Lane wrote:
>> I'm not particularly fussed about getting credit for that. However,
>> looking again at how that patch series turned out --- ie, that
>> we ensured POSIX behavior for NaNs only in HEAD --- I wonder
>> whether we shouldn't do what
Robert Haas writes:
> On Wed, Mar 28, 2018 at 9:56 PM, David G. Johnston
> wrote:
>> I made an argument for an "ANALYZE" grant a little while back, and it kinda
>> leads one to want one for VACUUM as well.
> Yeah, and FWIW, I think that's a totally reasonable request, as is
> this one. The prob
Nikita Glukhov writes:
> Experimenting with the new pluggable storage API, I found that amcanbackward
> flag is not checked in build_index_paths() before
> build_index_pathkeys(... BackwardScanDirection) call when we are building
> paths for ORDER BY. And this flag is even not copied into IndexOp
On 16 May 2018 at 08:10, Tom Lane wrote:
> David Rowley writes:
>> The attached patch implements the change.
>
> Please add to next CF. It's a bit late to be doing such things in v11,
> IMO.
If I do that, it'll go under bug fix. It seems strange to delay fixing
this until v12. We've still got 1
David Rowley writes:
> On 16 May 2018 at 08:10, Tom Lane wrote:
>> David Rowley writes:
>> Please add to next CF. It's a bit late to be doing such things in v11,
>> IMO.
> If I do that, it'll go under bug fix.
No, it should go under "planner improvement". If this were a bug fix,
it'd be a ca
fOn Wed, May 16, 2018 at 06:11:52AM +0900, Tatsuo Ishii wrote:
> >> This commit gives user-visible changes to the statment timeout
> >> behavior. So I think this should be added to the release notes.
> >
> > OK, makes sense. Here is what I added:
> >
> > 2017-09-18 [f8e5f156b] Rearm statement
On 16 May 2018 at 11:04, Tom Lane wrote:
> David Rowley writes:
>> On 16 May 2018 at 08:10, Tom Lane wrote:
>>> David Rowley writes:
>>> Please add to next CF. It's a bit late to be doing such things in v11,
>>> IMO.
>
>> If I do that, it'll go under bug fix.
>
> No, it should go under "planne
>> Can you please add Andres Freund to the author? He made extensive
>> changes to the original patch to improve it.
>
> Done.
Thanks!
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
> Change the ps process display labels to match the
> pg_stat_activity.backend_type labels (Peter Eisentraut)
pg_stat_activity.backend_type label for postgres process dedicated to
user sessions is "client backend" while ps still shows something like
"postgres: t-ishii postgres [local] idle". Do we
On Wed, May 16, 2018 at 08:33:53AM +0900, Tatsuo Ishii wrote:
> > Change the ps process display labels to match the
> > pg_stat_activity.backend_type labels (Peter Eisentraut)
>
> pg_stat_activity.backend_type label for postgres process dedicated to
> user sessions is "client backend" while ps sti
>> pg_stat_activity.backend_type label for postgres process dedicated to
>> user sessions is "client backend" while ps still shows something like
>> "postgres: t-ishii postgres [local] idle". Do we want to mention this?
>>
>> For example "Change the ps process display labels to match the
>> pg_sta
On Wed, May 16, 2018 at 08:52:05AM +0900, Tatsuo Ishii wrote:
> >> pg_stat_activity.backend_type label for postgres process dedicated to
> >> user sessions is "client backend" while ps still shows something like
> >> "postgres: t-ishii postgres [local] idle". Do we want to mention this?
> >>
> >>
There's a small typo.
> Add support for with huge(large) pages on Windows (Takayuki Tsunakawa, Thomas
> Munro)
I think a space between "huge" and "(large)" is needed.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.j
On Wed, May 16, 2018 at 09:01:35AM +0900, Tatsuo Ishii wrote:
> There's a small typo.
>
> > Add support for with huge(large) pages on Windows (Takayuki Tsunakawa,
> > Thomas Munro)
>
> I think a space between "huge" and "(large)" is needed.
Done, URL updated.
--
Bruce Momjian http
Hi Dmitry,
On Tue, May 15, 2018 at 11:10 PM, Dmitry Ivanov wrote:
> Is anybody still working on this? Are there any plans to add this to
> commitfest?
I am not actively working on this now, but I'll come back to it for
PG12 if you or Lukas don't beat me to it, and I'll help/test/review if
I you
At Tue, 15 May 2018 23:09:31 +0200, Manuel Kniep wrote in
> Dear hackers,
>
> I’m working on a foreign database wrapper for Kafka [1]
> Now I am trying to make it parallel aware. Following
> the documentation [2]
> However it seems that I can’t make it use more than a
> single worker with forc
On Mon, May 14, 2018 at 06:32:52PM -0400, Alvaro Herrera wrote:
> So, I don't know -- if the reaction is to add a #ifdef for pg version
> that adds a second argument passed always false, then we haven't won
> anything.
Yeah, that improves nothing..
>> What about naming those GetForeignServerExten
On Tue, May 15, 2018 at 02:32:55PM -0700, Andres Freund wrote:
> I have an *extremely* hard time that'd ever be the case. And it'd not
> really change much, given several years of back branch releases.
> Anyway, I'm only -0.1 here.
I personally don't care much if this gets in v11 or later in v12 a
On Mon, May 14, 2018 at 08:45:44PM -0400, Bruce Momjian wrote:
> What TLS does is to mix the offered ciphers into the negotiation hash so
> a man-in-the-middle can't pretend it doesn't support something. Could
> we do something like that here?
I have to admit that I don't quite follow here, the s
On Wed, May 16, 2018 at 12:17 AM, Bruce Momjian wrote:
> On Tue, May 15, 2018 at 08:45:07AM +0530, Amit Kapila wrote:
>> No, it is not like that. We divide the scan among workers and each
>> worker should perform projection of the rows it scanned (after
>> applying filter). Now, if the expensive
70 matches
Mail list logo
