On Wed, Aug 26, 2015 at 11:58 AM, Bruce Momjian wrote:
> I am sorry it so long for me to address this. Peter brought it up in
> June, but I just wasn't around to address it cleanly before now. I am
> glad he reminded me.
Well, you got around to it eventually. Thanks.
--
Peter Geoghegan
--
On Wed, Aug 26, 2015 at 02:47:14PM -0400, Bruce Momjian wrote:
> On Wed, Aug 26, 2015 at 10:10:01AM -0700, Peter Geoghegan wrote:
> > On Wed, Aug 26, 2015 at 7:33 AM, Bruce Momjian wrote:
> > > I have applied the attached patch to document this in the data type docs.
> >
> > Thanks, but shouldn't
On Wed, Aug 26, 2015 at 10:10:01AM -0700, Peter Geoghegan wrote:
> On Wed, Aug 26, 2015 at 7:33 AM, Bruce Momjian wrote:
> > I have applied the attached patch to document this in the data type docs.
>
> Thanks, but shouldn't varchar/text also be mentioned in the release
> notes, rather than "char
On Wed, Aug 26, 2015 at 7:33 AM, Bruce Momjian wrote:
> I have applied the attached patch to document this in the data type docs.
Thanks, but shouldn't varchar/text also be mentioned in the release
notes, rather than "character fields"?
--
Peter Geoghegan
--
Sent via pgsql-hackers mailing li
On Thu, Aug 20, 2015 at 04:07:36PM -0700, Peter Geoghegan wrote:
> On Sat, Jun 13, 2015 at 3:53 PM, Peter Geoghegan wrote:
> > I think we should really address this. Attached patch adds a new
> > release note item for it. It also adds to the documentation that
> > explains why users should prefer
Arthur Silva writes:
> Are we landing pg_tgrm 1.2 in pg 9.5?
No, we aren't.
And please don't quote 70 lines of unrelated stuff before making
your point.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your sub
On Sat, Jun 13, 2015 at 3:53 PM, Peter Geoghegan wrote:
> I think we should really address this. Attached patch adds a new
> release note item for it. It also adds to the documentation that
> explains why users should prefer varchar(n)/text to character(n); the
> lack of abbreviated key support no
On Sat, Aug 8, 2015 at 11:04 PM, Bruce Momjian wrote:
> On Sun, Aug 9, 2015 at 01:24:33AM +1200, David Rowley wrote:
> >
> > On 7 August 2015 at 14:24, Bruce Momjian wrote:
> >
> > On Tue, Jun 30, 2015 at 09:00:44PM +0200, Andres Freund wrote:
> > > * 2014-12-08 [519b075] Simon ..: Use
On Sun, Aug 9, 2015 at 01:24:33AM +1200, David Rowley wrote:
>
> On 7 August 2015 at 14:24, Bruce Momjian wrote:
>
> On Tue, Jun 30, 2015 at 09:00:44PM +0200, Andres Freund wrote:
> > * 2014-12-08 [519b075] Simon ..: Use GetSystemTimeAsFileTime directly in
> win32
> > 2014-12-
On Sat, Aug 8, 2015 at 02:49:21PM -0400, Bruce Momjian wrote:
> > > What I _am_ saying is that you should use the same criteria I am using,
> > > and just disagree on the place for the line, rather than use a different
> > > criteria, which will lead to perpetual complaints. We can change the
> >
On Fri, Aug 7, 2015 at 09:02:09PM +0200, Andres Freund wrote:
> On 2015-08-07 14:43:11 -0400, Bruce Momjian wrote:
> > Well, we could just throw a "Postgres 9.5 is faster" release note item
> > in there and call it a day. ;-)
>
> Based on my experience one of the prime reason people move to a ne
On Fri, Aug 7, 2015 at 09:02:09PM +0200, Andres Freund wrote:
> With regard to the point about the number of buffer mappings: This has
> forced peoples sites down. People have found this out themselves and
> patched postgres. That's an entirely different league.
I was not aware of the magnitude o
On 7 August 2015 at 14:24, Bruce Momjian wrote:
> On Tue, Jun 30, 2015 at 09:00:44PM +0200, Andres Freund wrote:
> > * 2014-12-08 [519b075] Simon ..: Use GetSystemTimeAsFileTime directly in
> win32
> > 2014-12-08 [8001fe6] Simon ..: Windows: use
> GetSystemTimePreciseAsFileTime if ..
> > Time
On Thu, Aug 6, 2015 at 10:35:50PM -0400, Bruce Momjian wrote:
> On Thu, Aug 6, 2015 at 06:42:38PM -0700, Peter Geoghegan wrote:
> > On Thu, Aug 6, 2015 at 6:08 PM, Bruce Momjian wrote:
> > > I though tabout this, and it is really an issue for FDW authors, not for
> > > end users, so I put this t
On 08/08/15 06:43, Bruce Momjian wrote:
On Fri, Aug 7, 2015 at 11:53:30AM -0400, Robert Haas wrote:
[...]
Well, we could just throw a "Postgres 9.5 is faster" release note item
in there and call it a day. ;-)
Nah! Just say it is Much Shinier, I'll buy it.
Unfortunately, we have to have much
On Fri, Aug 7, 2015 at 12:02 PM, Andres Freund wrote:
> Based on my experience one of the prime reason people move to a new
> version of postgres is performance. And it's not like 'faster!!!' is
> really helpful for them to evaluate the benefits appropriately. A
> scalability improvement isn't goi
On 2015-08-07 14:43:11 -0400, Bruce Momjian wrote:
> Well, we could just throw a "Postgres 9.5 is faster" release note item
> in there and call it a day. ;-)
Based on my experience one of the prime reason people move to a new
version of postgres is performance. And it's not like 'faster!!!' is
re
On Fri, Aug 7, 2015 at 11:53:30AM -0400, Robert Haas wrote:
> On Thu, Aug 6, 2015 at 10:24 PM, Bruce Momjian wrote:
> >> * 2014-10-02 [3acc10c9] Robert..: Increase the number of buffer mapping
> >> partition..
> >> should we mention this? This has been patched by a number of
> >> downstream
On 2015-08-07 11:53:30 -0400, Robert Haas wrote:
> On Thu, Aug 6, 2015 at 10:24 PM, Bruce Momjian wrote:
> >> * 2014-10-02 [3acc10c9] Robert..: Increase the number of buffer mapping
> >> partition..
> >> should we mention this? This has been patched by a number of
> >> downstream vendors and
On Thu, Aug 6, 2015 at 10:24 PM, Bruce Momjian wrote:
>> * 2014-10-02 [3acc10c9] Robert..: Increase the number of buffer mapping
>> partition..
>> should we mention this? This has been patched by a number of
>> downstream vendors and users, so it's probably worth calling out?
>
> Uh, I am not
On Thu, Aug 6, 2015 at 06:42:38PM -0700, Peter Geoghegan wrote:
> On Thu, Aug 6, 2015 at 6:08 PM, Bruce Momjian wrote:
> > I though tabout this, and it is really an issue for FDW authors, not for
> > end users, so I put this text in the Source Code changes section:
>
> I carefully considered whe
On Thu, Aug 6, 2015 at 11:19:46AM -0700, Jeff Janes wrote:
> On Wed, Jun 10, 2015 at 9:15 PM, Bruce Momjian wrote:
>
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
>
> and i
On Thu, Aug 6, 2015 at 10:21:29PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Tue, Jun 30, 2015 at 12:12:16AM +0200, Andres Freund wrote:
> >> Anyway, how about:
> >> format:%cd [%h] %<(8,trunc)%cN: %<(49,trunc)%s
> >> (which you can configure as pretty.pgmajor or so in .gitconfig btw.)
On Tue, Jun 30, 2015 at 09:00:44PM +0200, Andres Freund wrote:
> I've gone through the release notes and added comments referencing
> commits as discussed earlier. Additionally I've improved and added a
> bunch of items.
>
> Further stuff that came up while looking:
> * 2014-09-25 [b0d81ad] Heikki
Bruce Momjian writes:
> On Tue, Jun 30, 2015 at 12:12:16AM +0200, Andres Freund wrote:
>> Anyway, how about:
>> format:%cd [%h] %<(8,trunc)%cN: %<(49,trunc)%s
>> (which you can configure as pretty.pgmajor or so in .gitconfig btw.)
> Should we add this to src/tools/git_changelog? It currently use
On Thu, Aug 6, 2015 at 6:08 PM, Bruce Momjian wrote:
> I though tabout this, and it is really an issue for FDW authors, not for
> end users, so I put this text in the Source Code changes section:
I carefully considered where to put it, and chose the compatibility
section based on the precedent of
On Tue, Jun 30, 2015 at 12:12:16AM +0200, Andres Freund wrote:
> On 2015-06-29 17:58:54 -0400, Tom Lane wrote:
> > Yeah we are. The only places you'll find where we aren't formatting to 77
> > or 78 columns or so are where it would require breaking SGML tags in weird
> > places.
>
> Which isn't e
On Mon, Jun 29, 2015 at 05:05:59PM -0400, Tom Lane wrote:
> Andres Freund writes:
> > I'm working on integrating the suggestions I made last week to the
> > release notes. Would anybody mind if I start to add commit ids in
> > comments, similar to what Tom has done for minor releases, to news
> >
On Fri, Jun 26, 2015 at 03:39:19PM -0700, Peter Geoghegan wrote:
> On Wed, Jun 10, 2015 at 9:15 PM, Bruce Momjian wrote:
> > I am ready to make suggested adjustments
>
> I attach a compatibility note that is clearly needed; adding this is
> an open item of mine for 9.5. This concerns foreign data
On Thu, Aug 6, 2015 at 3:39 PM, Bruce Momjian wrote:
> I am using the same criteria I have always used. If you would like it
> changed, we need to discuss it at a macro level, not for individual
> cases where we feel someone didn't get enough _credit_.
I don't know how you can say that no *user*
On Thu, Aug 6, 2015 at 03:32:43PM -0700, Peter Geoghegan wrote:
> On Thu, Aug 6, 2015 at 3:06 PM, Bruce Momjian wrote:
> >> Below performance improvement in the "General Performance" category is
> >> missing:
> >>
> >> Reduce btree scan overhead for < and > strategies
> >>
> >> For <, <=
On Thu, Aug 6, 2015 at 3:06 PM, Bruce Momjian wrote:
>> Below performance improvement in the "General Performance" category is
>> missing:
>>
>> Reduce btree scan overhead for < and > strategies
>>
>> For <, <=, > and >= strategies, mark the first scan key
>> as already matched if sca
On Mon, Jun 22, 2015 at 09:14:01PM +, Rajeev rastogi wrote:
> On 11 June 2015 09:45, Bruce Momjian Wrote:
>
> >
> > I have committed the first draft of the 9.5 release notes. You can
> > view the output here:
> >
> > http://momjian.us/pgsql_docs/release-9-5.html
> >
> > and it will eve
On Fri, Jun 19, 2015 at 09:44:04PM +0200, Andres Freund wrote:
> Hi,
>
> On 2015-06-11 00:15:21 -0400, Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
>
> I'm looking through all the commits, checking which I think should
> po
On Thu, Aug 6, 2015 at 06:44:40PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > On Fri, Jun 19, 2015 at 08:21:19PM +0200, Andres Freund wrote:
>
> > > I think 647248e3708, 4fe384bd85, 4f85fde8, 59f71a0d0 should also be
> >
> > I couldn't look up 647248e3708, I got "unknown revision or
Bruce Momjian wrote:
> On Fri, Jun 19, 2015 at 08:21:19PM +0200, Andres Freund wrote:
> > I think 647248e3708, 4fe384bd85, 4f85fde8, 59f71a0d0 should also be
>
> I couldn't look up 647248e3708, I got "unknown revision or path not in
> the working tree."
a "6" is missing. 6647248e3708
--
Álvar
On Wed, Jun 24, 2015 at 11:34:27AM +0200, Andres Freund wrote:
> On 2015-06-23 21:08:36 -0400, Robert Haas wrote:
> > On Tue, Jun 23, 2015 at 5:48 PM, Kevin Grittner wrote:
> > > Andres Freund wrote:
> > >>>
> > >>>
> > >>>Improve concurrent locking and buffer scan performanc
On Fri, Jun 19, 2015 at 08:21:19PM +0200, Andres Freund wrote:
> Hi,
>
> On 2015-06-11 00:15:21 -0400, Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
>
> So, I did a pass through master's state:
>
> >
> >
> >
On Fri, Jun 26, 2015 at 3:39 PM, Peter Geoghegan wrote:
> I attach a compatibility note that is clearly needed; adding this is
> an open item of mine for 9.5. This concerns foreign data wrappers and
> UPSERT.
Can you look at this please, Bruce?
--
Peter Geoghegan
--
Sent via pgsql-hackers m
On Thu, Aug 6, 2015 at 01:48:26PM -0400, Robert Haas wrote:
> On Thu, Aug 6, 2015 at 10:33 AM, Bruce Momjian wrote:
> > On Sun, Jun 14, 2015 at 12:05:54PM +0100, Dean Rasheed wrote:
> >> On 11 June 2015 at 05:15, Bruce Momjian wrote:
> >> > I have committed the first draft of the 9.5 release not
On Wed, Jun 10, 2015 at 9:15 PM, Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
>
> and it will eventually appear here:
>
> http://www.postgresql.org/docs/devel/st
On Thu, Aug 6, 2015 at 10:33 AM, Bruce Momjian wrote:
> On Sun, Jun 14, 2015 at 12:05:54PM +0100, Dean Rasheed wrote:
>> On 11 June 2015 at 05:15, Bruce Momjian wrote:
>> > I have committed the first draft of the 9.5 release notes. You can view
>> > the output here:
>> >
>> > http://momj
On Sun, Jun 14, 2015 at 12:05:54PM +0100, Dean Rasheed wrote:
> On 11 June 2015 at 05:15, Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
> >
> > http://momjian.us/pgsql_docs/release-9-5.html
> >
>
> I think it's worth
On Fri, Jun 26, 2015 at 3:39 PM, Peter Geoghegan wrote:
> I attach a compatibility note that is clearly needed; adding this is
> an open item of mine for 9.5. This concerns foreign data wrappers and
> UPSERT.
Are you going to review this, Bruce? It is an open item for 9.5.
I would also like you
I've gone through the release notes and added comments referencing
commits as discussed earlier. Additionally I've improved and added a
bunch of items.
Further stuff that came up while looking:
* 2014-09-25 [b0d81ad] Heikki..: Add -D option to specify data directory to
pg_c..
new options, shoul
On 2015-06-29 17:58:54 -0400, Tom Lane wrote:
> Yeah we are. The only places you'll find where we aren't formatting to 77
> or 78 columns or so are where it would require breaking SGML tags in weird
> places.
Which isn't exactly infrequent...
Anyway, how about:
format:%cd [%h] %<(8,trunc)%cN: %<
Andres Freund writes:
> On 2015-06-29 17:44:06 -0400, Tom Lane wrote:
>> Ah yes, didn't see that option. That's definitely better. I'd still vote
>> for restricting it to fit in an 80-column window though.
> I don't see the benefit of truncating away the end of the commit message
> - that'll ju
On 2015-06-29 17:44:06 -0400, Tom Lane wrote:
> Andres Freund writes:
> > How about:
> > git log --pretty='format:%cd [%h] %cN: %s' --date=short upstream/master
>
> Ah yes, didn't see that option. That's definitely better. I'd still vote
> for restricting it to fit in an 80-column window though
Andres Freund writes:
> How about:
> git log --pretty='format:%cd [%h] %cN: %s' --date=short upstream/master
Ah yes, didn't see that option. That's definitely better. I'd still vote
for restricting it to fit in an 80-column window though.
regards, tom lane
--
Sent vi
On 2015-06-29 17:30:57 -0400, Tom Lane wrote:
> Andres Freund writes:
> > Haven't yet thought much about the format, maybe in the style of
> > git log --pretty='format:[%h] %aN [%ci]: %s' upstream/master
> > I'd personally like to see the hash and the time, the rest isn't
> > particularly importan
Andres Freund writes:
> Haven't yet thought much about the format, maybe in the style of
> git log --pretty='format:[%h] %aN [%ci]: %s' upstream/master
> I'd personally like to see the hash and the time, the rest isn't
> particularly important to me.
[ ... plays with that ... ] Hm. To keep down
On 2015-06-29 17:05:59 -0400, Tom Lane wrote:
> +1. Helps confirm which items are meant to correspond to which commits.
That's what made me think of it.
> In case you didn't realize it already, the stuff I put into the minor
> release notes is from src/tools/git_changelog. Dunno whether we need
Andres Freund writes:
> I'm working on integrating the suggestions I made last week to the
> release notes. Would anybody mind if I start to add commit ids in
> comments, similar to what Tom has done for minor releases, to news
> items?
+1. Helps confirm which items are meant to correspond to wh
Hi,
On 2015-06-11 00:15:21 -0400, Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes.
I'm working on integrating the suggestions I made last week to the
release notes. Would anybody mind if I start to add commit ids in
comments, similar to what Tom has done for minor
On Fri, Jun 26, 2015 at 3:39 PM, Peter Geoghegan wrote:
> On Wed, Jun 10, 2015 at 9:15 PM, Bruce Momjian wrote:
>> I am ready to make suggested adjustments
Also, I attach a new description of the UPSERT feature. For me, UPSERT
was always about guarantees that make statements work robustly under
On Wed, Jun 10, 2015 at 9:15 PM, Bruce Momjian wrote:
> I am ready to make suggested adjustments
I attach a compatibility note that is clearly needed; adding this is
an open item of mine for 9.5. This concerns foreign data wrappers and
UPSERT.
--
Peter Geoghegan
diff --git a/doc/src/sgml/releas
On Fri, Jun 26, 2015 at 2:37 PM, Peter Geoghegan wrote:
> On Fri, Jun 26, 2015 at 11:29 AM, Robert Haas wrote:
>>
>> OK, but how about this wording instead?
>
> That seems fine.
>
>> BTW, shouldn't Andrew also be credited here, since he did the work on
>> datum sorts?
>
> Andrew's work was entire
On Fri, Jun 26, 2015 at 11:29 AM, Robert Haas wrote:
>
> OK, but how about this wording instead?
That seems fine.
> BTW, shouldn't Andrew also be credited here, since he did the work on
> datum sorts?
Andrew's work was entirely confined to making datum sorts work with
abbreviation, which seems
On Fri, Jun 26, 2015 at 2:25 PM, Peter Geoghegan wrote:
> On Fri, Jun 26, 2015 at 9:29 AM, Robert Haas wrote:
>> Can you put your suggestions here in the form of a patch to the release
>> notes?
>
> The attached patch generalizes from the 9.2 release note wording. I
> use the word "inlined" here
On Fri, Jun 26, 2015 at 9:29 AM, Robert Haas wrote:
> Can you put your suggestions here in the form of a patch to the release notes?
The attached patch generalizes from the 9.2 release note wording. I
use the word "inlined" here too, even though commit 5ea86e6e6 did not
do too much with inlining
On Fri, Jun 26, 2015 at 2:01 PM, Alvaro Herrera
wrote:
> Robert Haas wrote:
>> On Thu, Jun 25, 2015 at 12:09 AM, Amit Langote
>> wrote:
>
>> > Is it intentional that the following items are separate?
>> > [...]
>> > Or could they made into one item?
>>
>> I think one item would be fine.
>
> I sug
Robert Haas wrote:
> On Thu, Jun 25, 2015 at 12:09 AM, Amit Langote
> wrote:
> > Is it intentional that the following items are separate?
> > [...]
> > Or could they made into one item?
>
> I think one item would be fine.
I suggested the same a couple of weeks ago.
--
Álvaro Herrera
On Thu, Jun 25, 2015 at 12:09 AM, Amit Langote
wrote:
> On 2015-06-11 PM 01:15, Bruce Momjian wrote:
>> I have committed the first draft of the 9.5 release notes. You can view
>> the output here:
>>
>> http://momjian.us/pgsql_docs/release-9-5.html
>>
>> and it will eventually appear here:
>
On Wed, Jun 24, 2015 at 6:47 PM, Peter Geoghegan wrote:
> On Sun, Jun 14, 2015 at 2:08 PM, Peter Geoghegan wrote:
>> Really? The pre-check thing wasn't too complex for Magnus to have a
>> couple of bullet points on it *specifically* in his high level NYC
>> talk on Postgres 9.5 features [1]. I do
Hi,
On 2015-06-11 PM 01:15, Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
>
> and it will eventually appear here:
>
> http://www.postgresql.org/docs/devel/st
On Sun, Jun 14, 2015 at 2:08 PM, Peter Geoghegan wrote:
> Really? The pre-check thing wasn't too complex for Magnus to have a
> couple of bullet points on it *specifically* in his high level NYC
> talk on Postgres 9.5 features [1]. I don't think it's hard to
> understand at all.
>
> Also, it's sim
On 2015-06-23 21:08:36 -0400, Robert Haas wrote:
> On Tue, Jun 23, 2015 at 5:48 PM, Kevin Grittner wrote:
> > Andres Freund wrote:
> >>>
> >>>
> >>>Improve concurrent locking and buffer scan performance (Andres
> >>>Freund, Kevin Grittner)
> >>>
> >>>
> >
On Tue, Jun 23, 2015 at 5:48 PM, Kevin Grittner wrote:
> Andres Freund wrote:
>>>
>>>
>>>Improve concurrent locking and buffer scan performance (Andres
>>>Freund, Kevin Grittner)
>>>
>>>
>>
>> If this is ab5194e6f, I don't think it makes sense to mention
Andres Freund wrote:
>>
>>
>>Improve concurrent locking and buffer scan performance (Andres
>>Freund, Kevin Grittner)
>>
>>
>
> If this is ab5194e6f, I don't think it makes sense to mention "buffer
> scan" - it's just any lwlock, and buffer locks aren't th
On 11 June 2015 09:45, Bruce Momjian Wrote:
>
> I have committed the first draft of the 9.5 release notes. You can
> view the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
>
> and it will eventually appear here:
>
> http://www.postgresql.org/docs/devel/static/rele
Hi,
On 2015-06-11 00:15:21 -0400, Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
I'm looking through all the commits, checking which I think should
possibly be mentioned additionally:
- 9f03ca91 - Speed up CREATE INDEX by avoidin
Hi,
On 2015-06-11 00:15:21 -0400, Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
So, I did a pass through master's state:
>
>
>Add Block Range Indexes (BRIN)
>(Álvaro Herrera, Heikki Linnakangas, Emr
Bruce Momjian wrote:
> On Sun, Jun 14, 2015 at 11:21:35AM -0400, Tom Lane wrote:
> > For pretty much the same reason, I'm not in favor of small caps either.
> > Even assuming we can do that consistently (which I bet we can't; we
> > do not have all that much control over how web browsers render HT
On Sun, Jun 14, 2015 at 11:21:35AM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > OK, new idea. What about, instead of having the last name be all-caps,
> > we have the last name start with an uppercase letter, then use smallcaps
> > for the rest of the last name:
> > https://en.wikipedia
On Sat, Jun 13, 2015 at 6:24 PM, Bruce Momjian wrote:
>> I think we should really address this. Attached patch adds a new
>> release note item for it. It also adds to the documentation that
>> explains why users should prefer varchar(n)/text to character(n); the
>> lack of abbreviated key support
On Sun, Jun 14, 2015 at 01:57:08PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > On Sat, Jun 13, 2015 at 05:47:59AM -0300, Alvaro Herrera wrote:
>
> > > Also, it looks like we could spell your last name with an accent,
> > > assuming the i-acute character in Latin1 is fine.
> >
> > Ah,
Bruce Momjian wrote:
> On Sat, Jun 13, 2015 at 05:47:59AM -0300, Alvaro Herrera wrote:
> > Also, it looks like we could spell your last name with an accent,
> > assuming the i-acute character in Latin1 is fine.
>
> Ah, you are correct. I found a few commits that did have that accent.
> All _sev
Bruce Momjian writes:
> OK, new idea. What about, instead of having the last name be all-caps,
> we have the last name start with an uppercase letter, then use smallcaps
> for the rest of the last name:
> https://en.wikipedia.org/wiki/Small_caps
> That way, the last name will not appear too
* Bruce Momjian (br...@momjian.us) wrote:
> On Sat, Jun 13, 2015 at 11:30:30PM -0400, Bruce Momjian wrote:
> > > Note that I guess "MauMau" is a nickname.
> >
> > I think we are fine consistenly putting Japanese last names first _if_
> > we always capitalize the last name, e.g. "FUJITA Etsuro" ---
On Sat, Jun 13, 2015 at 11:30:30PM -0400, Bruce Momjian wrote:
> > Note that I guess "MauMau" is a nickname.
>
> I think we are fine consistenly putting Japanese last names first _if_
> we always capitalize the last name, e.g. "FUJITA Etsuro" --- is that a
> good idea? Does everyone like that? Do
On 11 June 2015 at 05:15, Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
>
I think it's worth mentioning
dcbf5948e12aa60b4d6ab65b6445897dfc971e01, probably under "General
On 2015-06-14 03:02, Bruce Momjian wrote:
On Sat, Jun 13, 2015 at 05:47:59AM -0300, Alvaro Herrera wrote:
Petr Jelinek wrote:
Hi,
+
+
+Add JSONB functions jsonb_set() and
+jsonb_pretty (Dmitry Dolgov, Andrew Dunstan)
+
+
I believe I should be 3rd auth
On Sun, Jun 14, 2015 at 12:30 PM, Bruce Momjian wrote:
> On Sun, Jun 14, 2015 at 11:44:25AM +0900, Tatsuo Ishii wrote:
>> The real question here is, if contributors are required to show their
>> "official" names (along with their alias or nickname if any). If yes,
>> it is apparent that all contri
On Sun, Jun 14, 2015 at 11:44:25AM +0900, Tatsuo Ishii wrote:
> The real question here is, if contributors are required to show their
> "official" names (along with their alias or nickname if any). If yes,
> it is apparent that all contributor names should be shown in a unified
> formal style.
>
> Bruce Momjian wrote:
>> I have committed the first draft of the 9.5 release notes. You can view
>> the output here:
>>
>> http://momjian.us/pgsql_docs/release-9-5.html
>
> I noticed something while reading this and would like the input of our
> Japanese contributors.
>
> Normally, wester
On June 13, 2015 09:30:12 PM Bruce Momjian wrote:
> Are there other countries where this would be appropriate?
I'm pretty sure Hungarian uses the family name-given name ordering, and it's
also sometimes used in French, and therefore you often see French family names
spelled in all caps.
--
> On Sat, Jun 13, 2015 at 08:18:26PM -0300, Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > I have committed the first draft of the 9.5 release notes. You can view
> > > the output here:
> > >
> > > http://momjian.us/pgsql_docs/release-9-5.html
> >
> > I noticed something while reading this
Bruce Momjian wrote:
> On Sat, Jun 13, 2015 at 08:20:48PM -0300, Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > I have committed the first draft of the 9.5 release notes. You can view
> > > the output here:
> > >
> > > http://momjian.us/pgsql_docs/release-9-5.html
> >
> > One more thing
On Sat, Jun 13, 2015 at 08:18:26PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
> >
> > http://momjian.us/pgsql_docs/release-9-5.html
>
> I noticed something while reading this and would l
On Sat, Jun 13, 2015 at 03:53:43PM -0700, Peter Geoghegan wrote:
> On Thu, Jun 11, 2015 at 1:23 PM, Peter Geoghegan wrote:
> > I'm not sure if it's worth mentioning the "cheap equality for text"
> > commit (e246b3d6eac09). I guess that it probably is, because it will
> > help with things like inde
On Sat, Jun 13, 2015 at 08:20:48PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
> >
> > http://momjian.us/pgsql_docs/release-9-5.html
>
> One more thing on names. You have Alexander Shulg
On Sat, Jun 13, 2015 at 07:52:22AM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
> >
> > http://momjian.us/pgsql_docs/release-9-5.html
> >
> > and it will eventually appear here:
> >
>
On Sat, Jun 13, 2015 at 05:47:59AM -0300, Alvaro Herrera wrote:
> Petr Jelinek wrote:
> > Hi,
> >
> > +
> > +
> > +Add JSONB functions jsonb_set() and
> > +jsonb_pretty (Dmitry Dolgov, Andrew Dunstan)
> > +
> > +
> >
> > I believe I should be 3rd author f
On Sat, Jun 13, 2015 at 08:25:55AM +0530, Amit Kapila wrote:
> On Sat, Jun 13, 2015 at 7:47 AM, Bruce Momjian wrote:
> >
> > On Thu, Jun 11, 2015 at 09:02:35PM +0200, Magnus Hagander wrote:
> > > On Thu, Jun 11, 2015 at 8:56 PM, Josh Berkus wrote:
> > >
> > > On 06/10/2015 09:50 PM, Amit Kapi
Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
One more thing on names. You have Alexander Shulgin as Alex Shulgin in
the second place his name appears. Also, since he mov
Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
I noticed something while reading this and would like the input of our
Japanese contributors.
Normally, western names are wri
On Thu, Jun 11, 2015 at 1:23 PM, Peter Geoghegan wrote:
> I'm not sure if it's worth mentioning the "cheap equality for text"
> commit (e246b3d6eac09). I guess that it probably is, because it will
> help with things like index scans, too. Arguably that isn't a sorting
> thing (it's certainly not *
Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
>
> and it will eventually appear here:
>
> http://www.postgresql.org/docs/devel/static/release.html
>
> I am re
Petr Jelinek wrote:
> Hi,
>
> +
> +
> +Add JSONB functions jsonb_set() and
> +jsonb_pretty (Dmitry Dolgov, Andrew Dunstan)
> +
> +
>
> I believe I should be 3rd author for this one as I rewrote large parts of
> this functionality as part of the review.
A
On Sat, Jun 13, 2015 at 7:47 AM, Bruce Momjian wrote:
>
> On Thu, Jun 11, 2015 at 09:02:35PM +0200, Magnus Hagander wrote:
> > On Thu, Jun 11, 2015 at 8:56 PM, Josh Berkus wrote:
> >
> > On 06/10/2015 09:50 PM, Amit Kapila wrote:
> > > Also shall we mention about below in Migrations to 9.
1 - 100 of 133 matches
Mail list logo
