On Wed, Oct 10, 2018 at 06:13:56PM -0400, Bruce Momjian wrote:
> On Wed, Oct 10, 2018 at 06:06:01PM -0400, Bruce Momjian wrote:
> > On Wed, Oct 10, 2018 at 12:55:33PM -0700, Andres Freund wrote:
> > > Several people argued for introducing it, you're the only one that was
> > > against it. Adrien, A
On Wed, Oct 10, 2018 at 06:06:01PM -0400, Bruce Momjian wrote:
> On Wed, Oct 10, 2018 at 12:55:33PM -0700, Andres Freund wrote:
> > Several people argued for introducing it, you're the only one that was
> > against it. Adrien, Amit Kapila, Peter Geoghegan, and I all said we
> > think that kind of t
On Wed, Oct 10, 2018 at 12:55:33PM -0700, Andres Freund wrote:
> Hi,
>
> On 2018-10-08 21:28:02 -0400, Bruce Momjian wrote:
> > On Mon, Oct 8, 2018 at 05:44:32PM +0200, Adrien NAYRAT wrote:
> > > On 10/8/18 5:20 PM, Bruce Momjian wrote:
> > > >Uh, where are you looking? We don't rebuild the beta
Hi,
On 2018-10-08 21:28:02 -0400, Bruce Momjian wrote:
> On Mon, Oct 8, 2018 at 05:44:32PM +0200, Adrien NAYRAT wrote:
> > On 10/8/18 5:20 PM, Bruce Momjian wrote:
> > >Uh, where are you looking? We don't rebuild the beta docs until the
> > >next beta release, but you can see the changes in the
On Mon, Oct 8, 2018 at 05:44:32PM +0200, Adrien NAYRAT wrote:
> On 10/8/18 5:20 PM, Bruce Momjian wrote:
> >Uh, where are you looking? We don't rebuild the beta docs until the
> >next beta release, but you can see the changes in the developer docs:
> >
> > https://www.postgresql.org/docs/deve
On 10/8/18 5:20 PM, Bruce Momjian wrote:
Uh, where are you looking? We don't rebuild the beta docs until the
next beta release, but you can see the changes in the developer docs:
https://www.postgresql.org/docs/devel/static/release-11.html
I looked in doc/src/sgml/release-11.sgml
And
On Mon, Oct 8, 2018 at 12:05:03PM +0200, Adrien NAYRAT wrote:
> On 9/20/18 8:47 AM, Adrien Nayrat wrote:
> >On 8/25/18 11:24 PM, Peter Geoghegan wrote:
> >>On Sat, Aug 25, 2018 at 2:18 PM, Bruce Momjian wrote:
> I think that's less "our" logic and more yours, that has become
> established
On 9/20/18 8:47 AM, Adrien Nayrat wrote:
On 8/25/18 11:24 PM, Peter Geoghegan wrote:
On Sat, Aug 25, 2018 at 2:18 PM, Bruce Momjian wrote:
I think that's less "our" logic and more yours, that has become
established because you've done most of the major release notes for a
long time. I'm not tr
On 10/5/18 5:22 PM, Bruce Momjian wrote:
> On Fri, Oct 5, 2018 at 03:28:41PM -0400, Jonathan Katz wrote:
>> On 9/27/18 9:21 PM, Amit Langote wrote:
>>> Yeah, "any other partition" is what the existing description uses too, so:
>>>
>>> Having a "default" partition for storing data that does not mat
On Fri, Oct 5, 2018 at 03:28:41PM -0400, Jonathan Katz wrote:
> On 9/27/18 9:21 PM, Amit Langote wrote:
> > Yeah, "any other partition" is what the existing description uses too, so:
> >
> > Having a "default" partition for storing data that does not match any
> > other partition
>
> Sorry for t
On 9/27/18 9:21 PM, Amit Langote wrote:
> On 2018/09/27 23:24, Alvaro Herrera wrote:
>> On 2018-Sep-27, Amit Langote wrote:
>>
>>> Sorry I couldn't reply sooner, but the following of your proposed text
>>> needs to be updated a bit:
>>>
>>> +
>>> +
>>> + Having a "default" pa
On Sat, Sep 29, 2018 at 04:28:13PM +0900, Amit Langote wrote:
> > The default partition can store rows that don't match any of the
> > other defined partitions, and is searched accordingly.
>
> I was commenting on the Jonathan's patch upthread [1] whereby he
> proposed to add a lin
On Fri, Sep 28, 2018 at 7:24 PM Bruce Momjian wrote:
> On Fri, Sep 28, 2018 at 10:21:16AM +0900, Amit Langote wrote:
> > On 2018/09/27 23:24, Alvaro Herrera wrote:
> > > On 2018-Sep-27, Amit Langote wrote:
> > >
> > >> Sorry I couldn't reply sooner, but the following of your proposed text
> > >> n
On Fri, Sep 28, 2018 at 10:21:16AM +0900, Amit Langote wrote:
> On 2018/09/27 23:24, Alvaro Herrera wrote:
> > On 2018-Sep-27, Amit Langote wrote:
> >
> >> Sorry I couldn't reply sooner, but the following of your proposed text
> >> needs to be updated a bit:
> >>
> >> +
> >> +
> >>
On 2018/09/27 23:24, Alvaro Herrera wrote:
> On 2018-Sep-27, Amit Langote wrote:
>
>> Sorry I couldn't reply sooner, but the following of your proposed text
>> needs to be updated a bit:
>>
>> +
>> +
>> + Having a "default" partition for storing data that does not match a
>>
On 2018-Sep-27, Amit Langote wrote:
> Sorry I couldn't reply sooner, but the following of your proposed text
> needs to be updated a bit:
>
> +
> +
> + Having a "default" partition for storing data that does not match a
> + partition key
> +
> +
>
>
Hi,
On 2018/09/17 1:07, Jonathan S. Katz wrote:
> On 9/16/18 11:36 AM, Bruce Momjian wrote:
>> On Sat, Sep 15, 2018 at 11:06:04AM -0400, Jonathan Katz wrote:
>>> @@ -2414,12 +2408,8 @@ same commits as above
>>> The option --create-slot creates
>>> the named replication slot (--sl
On 8/25/18 11:24 PM, Peter Geoghegan wrote:
> On Sat, Aug 25, 2018 at 2:18 PM, Bruce Momjian wrote:
>>> I think that's less "our" logic and more yours, that has become
>>> established because you've done most of the major release notes for a
>>> long time. I'm not trying to say that that's wrong o
On 9/16/18 11:36 AM, Bruce Momjian wrote:
> On Sat, Sep 15, 2018 at 11:06:04AM -0400, Jonathan Katz wrote:
>> @@ -2414,12 +2408,8 @@ same commits as above
>> The option --create-slot creates
>> the named replication slot (--slot)
>> when the WAL streaming method
>> -
On Sat, Sep 15, 2018 at 11:06:04AM -0400, Jonathan Katz wrote:
> @@ -2414,12 +2408,8 @@ same commits as above
> The option --create-slot creates
> the named replication slot (--slot)
> when the WAL streaming method
> -(--wal-method=stream) is used.
> -
> -
On 9/16/18 11:14 AM, Bruce Momjian wrote:
> On Sat, Sep 15, 2018 at 11:06:04AM -0400, Jonathan Katz wrote:
>>
>>
>> - Partitioning by a hash key
>> + Partitioning by a hash key (a.k.a. "hash partitioning")
>
> I question whether a.k.a (also known as) is familiar
On Sat, Sep 15, 2018 at 11:06:04AM -0400, Jonathan Katz wrote:
>
>
> - Partitioning by a hash key
> + Partitioning by a hash key (a.k.a. "hash partitioning")
I question whether a.k.a (also known as) is familiar enough to our
readers to appear in the releaes notes
Hi,
On 9/12/18 1:34 PM, Michael Banck wrote:
> Hi,
>
> On Fri, May 11, 2018 at 11:08:52AM -0400, 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:
>>
Hi,
On Fri, May 11, 2018 at 11:08:52AM -0400, 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/release-11.html
The first ite
On Sun, Aug 26, 2018 at 12:17 AM Bruce Momjian wrote:
>
> On Sat, Aug 25, 2018 at 11:42:35AM -0700, Andres Freund wrote:
> >
> >
> > On August 25, 2018 11:41:11 AM PDT, Bruce Momjian wrote:
> > >On Sun, Aug 12, 2018 at 11:21:26AM +0200, Adrien Nayrat wrote:
> > >> Hello,
> > >>
> > >> It seems th
On Sat, Aug 25, 2018 at 2:18 PM, Bruce Momjian wrote:
>> I think that's less "our" logic and more yours, that has become
>> established because you've done most of the major release notes for a
>> long time. I'm not trying to say that that's wrong or anything, just
>
> I don't do my work in a vacu
On Sat, Aug 25, 2018 at 12:17:17PM -0700, Andres Freund wrote:
> Hi,
>
> On 2018-08-25 14:47:20 -0400, Bruce Momjian wrote:
> > Well, our normal logical is whether the average user would adjust their
> > behavior based on this change, or whether it is user visible. I thought
> > it was a contrive
Hi,
On 2018-08-25 14:47:20 -0400, Bruce Momjian wrote:
> Well, our normal logical is whether the average user would adjust their
> behavior based on this change, or whether it is user visible. I thought
> it was a contrived-enough query that this was not the case, but I would
> be interested to h
On Sat, Aug 25, 2018 at 11:42:35AM -0700, Andres Freund wrote:
>
>
> On August 25, 2018 11:41:11 AM PDT, Bruce Momjian wrote:
> >On Sun, Aug 12, 2018 at 11:21:26AM +0200, Adrien Nayrat wrote:
> >> Hello,
> >>
> >> It seems this feature is missing in releases notes ?
> >>
> >> commit 1f6d515a67
On August 25, 2018 11:41:11 AM PDT, Bruce Momjian wrote:
>On Sun, Aug 12, 2018 at 11:21:26AM +0200, Adrien Nayrat wrote:
>> Hello,
>>
>> It seems this feature is missing in releases notes ?
>>
>> commit 1f6d515a67ec98194c23a5db25660856c9aab944
>> Author: Robert Haas
>> Date: Mon Aug 21 14:
On Sun, Aug 12, 2018 at 11:21:26AM +0200, Adrien Nayrat wrote:
> Hello,
>
> It seems this feature is missing in releases notes ?
>
> commit 1f6d515a67ec98194c23a5db25660856c9aab944
> Author: Robert Haas
> Date: Mon Aug 21 14:43:01 2017 -0400
>
> Push limit through subqueries to underlying
On Fri, Aug 10, 2018 at 7:10 PM, Alexander Korotkov
wrote:
> On Fri, Aug 10, 2018 at 8:08 AM Masahiko Sawada
> wrote:
>>
>> I found that the release note says "Add pgtrgm function
>> strict_word_similarity() to compute the similarity of whole words" but
>> I think "pgtrgm" should be "pg_trgm". At
Hello,
It seems this feature is missing in releases notes ?
commit 1f6d515a67ec98194c23a5db25660856c9aab944
Author: Robert Haas
Date: Mon Aug 21 14:43:01 2017 -0400
Push limit through subqueries to underlying sort, where possible.
Douglas Doole, reviewed by Ashutosh Bapat and by me.
On Fri, Aug 10, 2018 at 8:08 AM Masahiko Sawada
wrote:
> I found that the release note says "Add pgtrgm function
> strict_word_similarity() to compute the similarity of whole words" but
> I think "pgtrgm" should be "pg_trgm". Attached patch fixes it.
>
Right. Pushed, thanks!
--
Alexander K
Hi,
I found that the release note says "Add pgtrgm function
strict_word_similarity() to compute the similarity of whole words" but
I think "pgtrgm" should be "pg_trgm". Attached patch fixes it.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
"Jonathan S. Katz" writes:
> On Jun 30, 2018, at 5:52 PM, Tom Lane wrote:
>> Mmm, yeah, I suppose it should say "all framing options" rather than
>> implying that we've implemented every other window-related frammish
>> there is in the spec.
> +1. Attached patch that does exactly that.
Pushed,
On 2018-07-09 16:52:11 +0200, David Fetter wrote:
> On Mon, Jul 09, 2018 at 10:36:30AM -0400, Bruce Momjian wrote:
> > On Sun, Jul 8, 2018 at 10:28:15PM -0700, Andres Freund wrote:
> > > On 2018-07-09 14:18:14 +0900, Tatsuro Yamada wrote:
> > > > Hi Bruce,
> > > >
> > > > > I expect a torrent of
On 2018/07/09 23:52, David Fetter wrote:
On Mon, Jul 09, 2018 at 10:36:30AM -0400, Bruce Momjian wrote:
On Sun, Jul 8, 2018 at 10:28:15PM -0700, Andres Freund wrote:
On 2018-07-09 14:18:14 +0900, Tatsuro Yamada wrote:
Hi Bruce,
I expect a torrent of feedback.;-)
Could you add this fix to
On Mon, Jul 09, 2018 at 10:36:30AM -0400, Bruce Momjian wrote:
> On Sun, Jul 8, 2018 at 10:28:15PM -0700, Andres Freund wrote:
> > On 2018-07-09 14:18:14 +0900, Tatsuro Yamada wrote:
> > > Hi Bruce,
> > >
> > > > I expect a torrent of feedback.;-)
> > >
> > > Could you add this fix to the releas
On Sun, Jul 8, 2018 at 10:28:15PM -0700, Andres Freund wrote:
> On 2018-07-09 14:18:14 +0900, Tatsuro Yamada wrote:
> > Hi Bruce,
> >
> > > I expect a torrent of feedback.;-)
> >
> > Could you add this fix to the release note because this change affects
> > an extension developer using the hook
On 2018-07-09 14:18:14 +0900, Tatsuro Yamada wrote:
> Hi Bruce,
>
> > I expect a torrent of feedback.;-)
>
> Could you add this fix to the release note because this change affects
> an extension developer using the hook function.
> It would be better to know the change by reading the release note
Hi Bruce,
> I expect a torrent of feedback.;-)
Could you add this fix to the release note because this change affects
an extension developer using the hook function.
It would be better to know the change by reading the release note, not
compilation error.
Add QueryEnvironment
> On Jun 30, 2018, at 5:52 PM, Tom Lane wrote:
>
> Yaroslav writes:
>> I've noticed the following in v11 release notes:
>> "Window functions now support all options shown in the SQL:2011 standard,
>> including RANGE distance PRECEDING/FOLLOWING, GROUPS mode, and frame
>> exclusion options"
>
>
Yaroslav writes:
> I've noticed the following in v11 release notes:
> "Window functions now support all options shown in the SQL:2011 standard,
> including RANGE distance PRECEDING/FOLLOWING, GROUPS mode, and frame
> exclusion options"
> But, as far as I see, IGNORE NULLS option for lead, lag, et
Hello.
I've noticed the following in v11 release notes:
"Window functions now support all options shown in the SQL:2011 standard,
including RANGE distance PRECEDING/FOLLOWING, GROUPS mode, and frame
exclusion options"
But, as far as I see, IGNORE NULLS option for lead, lag, etc. is still not
supp
> On Jun 30, 2018, at 2:48 PM, Daniel Gustafsson wrote:
>
>> On 30 Jun 2018, at 20:11, Brad DeJong wrote:
>>
>> I suggest the following edits for the PostgreSQL beta 2 release announcement.
>> I did not provide the edits as a patch because I can't find the source of
>> /about/news/1867.
>
>
> On 30 Jun 2018, at 20:11, Brad DeJong wrote:
>
> I suggest the following edits for the PostgreSQL beta 2 release announcement.
> I did not provide the edits as a patch because I can't find the source of
> /about/news/1867.
The news item is stored in the postgresql.org database, and not in the
I suggest the following edits for the PostgreSQL beta 2 release
announcement.
I did not provide the edits as a patch because I can't find the source of
/about/news/1867.
- This release contains ... as well as bug fixes that were reported ...
+ This release contains ... as well as fixes for bugs th
On Tue, Jun 19, 2018 at 1:40 PM Alexander Korotkov
wrote:
> On Tue, Jun 19, 2018 at 12:15 PM Alexander Korotkov
> wrote:
> > On Sat, Jun 16, 2018 at 3:57 PM Darafei "Komяpa" Praliaskouski
> > wrote:
> > >>
> > >> > I'm not sure it is usefull in release notes since it is more about
> > >> > API,
On Tue, Jun 19, 2018 at 6:18 PM Daniel Gustafsson wrote:
> > On 19 Jun 2018, at 12:40, Alexander Korotkov
> > wrote:
> >
> > On Tue, Jun 19, 2018 at 12:15 PM Alexander Korotkov
> > wrote:
> >> On Sat, Jun 16, 2018 at 3:57 PM Darafei "Komяpa" Praliaskouski
> >> wrote:
>
> > I'm not sur
> On 19 Jun 2018, at 12:40, Alexander Korotkov
> wrote:
>
> On Tue, Jun 19, 2018 at 12:15 PM Alexander Korotkov
> wrote:
>> On Sat, Jun 16, 2018 at 3:57 PM Darafei "Komяpa" Praliaskouski
>> wrote:
> I'm not sure it is usefull in release notes since it is more about API,
> and no
On Tue, Jun 19, 2018 at 12:15 PM Alexander Korotkov
wrote:
> On Sat, Jun 16, 2018 at 3:57 PM Darafei "Komяpa" Praliaskouski
> wrote:
> >>
> >> > I'm not sure it is usefull in release notes since it is more about API,
> >> > and not
> >> > user-facing change. Just in case.
> >> > GiST opclasses n
On Sat, Jun 16, 2018 at 3:57 PM Darafei "Komяpa" Praliaskouski
wrote:
>>
>> > I'm not sure it is usefull in release notes since it is more about API,
>> > and not
>> > user-facing change. Just in case.
>> > GiST opclasses now can omit compress and decompress functions. If compress
>> > function i
>
> > I'm not sure it is usefull in release notes since it is more about API,
> and not
> > user-facing change. Just in case.
> > GiST opclasses now can omit compress and decompress functions. If
> compress
> > function is omited, IndexOnlyScan is enabled for opclass without any
> extra
> > change.
On Sat, Jun 09, 2018 at 01:35:19PM -0700, David G. Johnston wrote:
> On Fri, May 11, 2018 at 8:08 AM, 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:
&g
> On Jun 9, 2018, at 4:35 PM, David G. Johnston
> wrote:
>
> On Fri, May 11, 2018 at 8:08 AM, Bruce Momjian <mailto:br...@momjian.us>> wrote:
> I have committed the first draft of the Postgres 11 release notes. I
> will add more markup soon. You can view th
On Fri, May 11, 2018 at 8:08 AM, 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/release-11.html
Some thoughts:
As a
On Tue, May 22, 2018 at 11:31:08PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Fri, May 18, 2018 at 10:28:12AM -0400, Tom Lane wrote:
> >> While we're all griping about omissions from the release notes ...
> >> I think you should have documented that we fixed plpgsql to cope
> >> (or cop
Bruce Momjian writes:
> On Fri, May 18, 2018 at 10:28:12AM -0400, Tom Lane wrote:
>> While we're all griping about omissions from the release notes ...
>> I think you should have documented that we fixed plpgsql to cope
>> (or cope better, at least) with intrasession changes in the rowtypes
>> of
On Wed, May 23, 2018 at 02:06:15PM +1200, David Rowley wrote:
> On 23 May 2018 at 13:18, Bruce Momjian wrote:
> > On Mon, May 21, 2018 at 07:34:18PM +1200, David Rowley wrote:
> >> I've been working a bit in this area over the past few weeks and with
> >> PG11 I measured a single INSERT into a 10k
On Wed, May 23, 2018 at 11:55:29AM +1000, Haribabu Kommi wrote:
> Yes, security labels also gets dumped only with --create option.
OK.
> Can you update the author name as (Haribabu Kommi) to make it consistent
> with other entries.
Done. Applied patch attached.
--
Bruce Momjian htt
On 23 May 2018 at 13:18, Bruce Momjian wrote:
> On Mon, May 21, 2018 at 07:34:18PM +1200, David Rowley wrote:
>> I've been working a bit in this area over the past few weeks and with
>> PG11 I measured a single INSERT into a 10k RANGE partitioned table at
>> just 84 tps (!), while inserting the sa
On Wed, May 23, 2018 at 11:34 AM, Bruce Momjian wrote:
> On Mon, May 21, 2018 at 06:28:36PM +1000, Haribabu Kommi wrote:
> > On Sat, May 12, 2018 at 1:08 AM, Bruce Momjian wrote:
> >
> > I have committed the first draft of the Postgres 11 release notes. I
> >
On 2018/05/23 10:36, Bruce Momjian wrote:
> On Wed, May 23, 2018 at 10:28:41AM +0900, Amit Langote wrote:
>>> Uh, we already have this in the release notes:
>>>
>>> Allow faster partition elimination during query processing (Amit
>>> Langote, David Rowley, Dilip Kumar)
>>>
>>>
On Wed, May 23, 2018 at 01:37:22PM +1200, Thomas Munro wrote:
> On Sat, May 19, 2018 at 2:28 AM, Tom Lane wrote:
> > While we're all griping about omissions from the release notes ...
>
> Hi Bruce,
>
>
> Add support for ARMv8 hardware
> CRC calculations (Yuqi Gu, Heikki L
On Sat, May 19, 2018 at 2:28 AM, Tom Lane wrote:
> While we're all griping about omissions from the release notes ...
Hi Bruce,
Add support for ARMv8 hardware
CRC calculations (Yuqi Gu, Heikki Linnakangas)
Could I please ask for a third author credit for this one
On Wed, May 23, 2018 at 10:28:41AM +0900, Amit Langote wrote:
> > Uh, we already have this in the release notes:
> >
> > Allow faster partition elimination during query processing (Amit
> > Langote, David Rowley, Dilip Kumar)
> >
> > This speeds access to partitioned table
On Mon, May 21, 2018 at 06:28:36PM +1000, Haribabu Kommi wrote:
> On Sat, May 12, 2018 at 1:08 AM, 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
On 2018/05/23 10:16, Bruce Momjian wrote:
> On Sat, May 19, 2018 at 12:58:04AM +0900, Amit Langote wrote:
>> Hi Bruce.
>>
>> On Tue, May 15, 2018 at 12:46 PM, Amit Langote
>> wrote:
>>> On 2018/05/15 5:30, Bruce Momjian wrote:
I like it, done.
>>>
>>> Thank you.
>>
>> I wonder what you think
On Mon, May 21, 2018 at 07:34:18PM +1200, David Rowley wrote:
> On 19 May 2018 at 03:58, Amit Langote wrote:
> > I wonder what you think about including this little performance item:
> >
> > https://www.postgresql.org/message-id/e1eotsq-0005v0...@gemulon.postgresql.org
> >
> > especially consideri
On Sat, May 19, 2018 at 12:58:04AM +0900, Amit Langote wrote:
> Hi Bruce.
>
> On Tue, May 15, 2018 at 12:46 PM, Amit Langote
> wrote:
> > On 2018/05/15 5:30, Bruce Momjian wrote:
> >> I like it, done.
> >
> > Thank you.
>
> I wonder what you think about including this little performance item:
>
On Fri, May 18, 2018 at 10:28:12AM -0400, Tom Lane wrote:
> While we're all griping about omissions from the release notes ...
> I think you should have documented that we fixed plpgsql to cope
> (or cope better, at least) with intrasession changes in the rowtypes
> of composite-type variables. Se
>-Original Message-
>From: Bruce Momjian [mailto:br...@momjian.us]
>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:
Hi, there is a small typo.
I think "These functi
> On May 21, 2018, at 12:38 PM, Tom Lane wrote:
>
> "Jonathan S. Katz" writes:
>> Per feedback from many asynchronous threads, attached is the proposed
>> patch for the list of major features. I also expect a torrent of feedback. I
>> will have a corresponding press release for Beta 1 in the ve
"Jonathan S. Katz" writes:
> Per feedback from many asynchronous threads, attached is the proposed
> patch for the list of major features. I also expect a torrent of feedback. I
> will have a corresponding press release for Beta 1 in the very near future.
> This being my first doc patch proposal,
On Mon, May 21, 2018 at 4:34 PM, David Rowley
wrote:
> On 19 May 2018 at 03:58, Amit Langote wrote:
>> I wonder what you think about including this little performance item:
>>
>> https://www.postgresql.org/message-id/e1eotsq-0005v0...@gemulon.postgresql.org
>>
>> especially considering the part o
On Sat, May 12, 2018 at 1:08 AM, 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/release-11.html
>
Thanks for prepar
On 19 May 2018 at 03:58, Amit Langote wrote:
> I wonder what you think about including this little performance item:
>
> https://www.postgresql.org/message-id/e1eotsq-0005v0...@gemulon.postgresql.org
>
> especially considering the part of the commit message which states
>
> ...Still, testing shows
Hi Bruce.
On Tue, May 15, 2018 at 12:46 PM, Amit Langote
wrote:
> On 2018/05/15 5:30, Bruce Momjian wrote:
>> I like it, done.
>
> Thank you.
I wonder what you think about including this little performance item:
https://www.postgresql.org/message-id/e1eotsq-0005v0...@gemulon.postgresql.org
esp
> On May 11, 2018, at 11:08 AM, 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/release-11.html
>
> I expe
While we're all griping about omissions from the release notes ...
I think you should have documented that we fixed plpgsql to cope
(or cope better, at least) with intrasession changes in the rowtypes
of composite-type variables. See bug #15203 for the latest in a long
line of user complaints abou
On Fri, May 18, 2018 at 10:56:25AM +0500, Andrey Borodin wrote:
> H, Bruce!
>
>
> 11 мая 2018 г., в 20:08, Bruce Momjian написал(а):
>
> I expect a torrent of feedback. ;-)
>
>
> I'm not sure it is usefull in release notes since it is more about API, and
> not
> user-facing change.
On Tue, May 15, 2018 at 2:11 AM, Bruce Momjian wrote:
> On Mon, May 14, 2018 at 05:34:54PM +0530, Dilip Kumar wrote:
>>
>> On Fri, May 11, 2018 at 8:38 PM, Bruce Momjian wrote:
>>
>> I have committed the first draft of the Postgres 11 release notes. I
>>
H, Bruce!
> 11 мая 2018 г., в 20:08, Bruce Momjian написал(а):
>
> I expect a torrent of feedback. ;-)
I'm not sure it is usefull in release notes since it is more about API, and not
user-facing change. Just in case.
GiST opclasses now can omit compress and decompress functions. If compress
On Thu, May 17, 2018 at 02:23:00PM -0400, Bruce Momjian wrote:
> On Thu, May 17, 2018 at 10:35:53PM +0900, Michael Paquier wrote:
> > Hi Bruce,
> >
> > Here is some bonus feedback.
> >
> > On Fri, May 11, 2018 at 11:08:52AM -0400, Bruce Momjian wrote:
> > > I expect a torrent of feedback. ;-)
>
On Thu, May 17, 2018 at 10:35:53PM +0900, Michael Paquier wrote:
> Hi Bruce,
>
> Here is some bonus feedback.
>
> On Fri, May 11, 2018 at 11:08:52AM -0400, Bruce Momjian wrote:
> > I expect a torrent of feedback. ;-)
>
> I have just noticed that this entry does not have the correct author
> (gu
Huong Dangminh writes:
> Thank you. The patch looks fine to me.
> Also, I have done the "make check" in Windows and Linux environment with no
> problem.
Pushed, thanks for reviewing/testing.
regards, tom lane
On Thu, May 17, 2018 at 09:48:54PM +0900, Michael Paquier wrote:
> On Wed, May 16, 2018 at 09:09:22PM -0400, Bruce Momjian wrote:
> > On Thu, May 17, 2018 at 09:56:49AM +0900, Michael Paquier wrote:
> >> On Wed, May 16, 2018 at 08:20:49PM -0400, Bruce Momjian wrote:
> >>> SCRAM-with-binding is the
On Wed, May 16, 2018 at 09:09:22PM -0400, Bruce Momjian wrote:
> > > FYI, I think the server could also require channel binding for SCRAM. We
> > > already have scram-sha-256 in pg_hba.conf, and I think
> > > scram-sha-256-plus would be reasonable.
> >
> > Noted as well. There is of course the qu
On Thu, May 17, 2018 at 2:56 AM, Michael Paquier
wrote:
> On Wed, May 16, 2018 at 08:20:49PM -0400, Bruce Momjian wrote:
> > SCRAM-with-binding is the first password method that attempts to avoid
> > man-in-the-middle attacks, and therefore is much less likely to be able
> > to trust what the end
Hi Bruce,
Here is some bonus feedback.
On Fri, May 11, 2018 at 11:08:52AM -0400, Bruce Momjian wrote:
> I expect a torrent of feedback. ;-)
I have just noticed that this entry does not have the correct author
(guess who?):
Add libpq option to support channel binding when using SCRAM
On Wed, May 16, 2018 at 09:09:22PM -0400, Bruce Momjian wrote:
> On Thu, May 17, 2018 at 09:56:49AM +0900, Michael Paquier wrote:
>> On Wed, May 16, 2018 at 08:20:49PM -0400, Bruce Momjian wrote:
>>> SCRAM-with-binding is the first password method that attempts to avoid
>>> man-in-the-middle attack
Hi,
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> 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 N
On Thu, May 17, 2018 at 5:54 AM, Bruce Momjian wrote:
>
> Oh, sorry, changed to:
>
> Allow single-evaluation queries, e.g. WHERE
> clause aggregate queries, and functions in the target list to be
> parallelized (Amit Kapila, Robert Haas)
>
LGTM. Thanks.
--
With Regards
On Thu, May 17, 2018 at 09:56:49AM +0900, Michael Paquier wrote:
> On Wed, May 16, 2018 at 08:20:49PM -0400, Bruce Momjian wrote:
> > SCRAM-with-binding is the first password method that attempts to avoid
> > man-in-the-middle attacks, and therefore is much less likely to be able
> > to trust what
On Wed, May 16, 2018 at 08:20:49PM -0400, Bruce Momjian wrote:
> SCRAM-with-binding is the first password method that attempts to avoid
> man-in-the-middle attacks, and therefore is much less likely to be able
> to trust what the endpoints supports. I think it is really the
> channel_binding_mode
On Wed, May 16, 2018 at 10:08:18AM -0400, Alvaro Herrera wrote:
> On 2018-May-15, Bruce Momjian wrote:
>
> > 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,
> > > > Thom
On Wed, May 16, 2018 at 01:50:04PM +0300, Heikki Linnakangas wrote:
> >* Allow bytes to be specified for server variable sizes (Beena Emerson)
> >
> >The specification is "B".
>
> I had to dig the commit in the git history to figure out what this is. I'd
> suggest rewording this:
>
> * Allow serv
On Wed, May 16, 2018 at 09:55:05AM +0530, Amit Kapila wrote:
> 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 t
On Wed, May 16, 2018 at 08:59:23PM +0900, Michael Paquier wrote:
> On Wed, May 16, 2018 at 01:09:07PM +0300, Heikki Linnakangas wrote:
> > I have to agree with Bruce, that it's pretty useless to implement channel
> > binding, if there is no way to require it in libpq. IMHO that must be
> > fixed.
>
1 - 100 of 188 matches
Mail list logo
