On Mon, Aug 6, 2018 at 11:17 PM, Jonathan S. Katz
wrote:
>
> > On Aug 6, 2018, at 3:37 PM, Tom Lane wrote:
> >
> > "Jonathan S. Katz" writes:
> >>> On Aug 6, 2018, at 3:27 PM, Tom Lane wrote:
> >>> Actually, a concrete reason why that might not be good is that it
> results
> >>> in having a si
On Fri, Aug 10, 2018 at 1:38 AM, Peter Eisentraut <
peter.eisentr...@2ndquadrant.com> wrote:
> On 06/08/2018 00:57, Tom Lane wrote:
> > Anyway, I'd like to propose a compromise position that I don't think
> > has been discussed before: let's drop release notes for branches
> > that were already EO
On Mon, Aug 6, 2018 at 9:37 PM, Tom Lane wrote:
> "Jonathan S. Katz" writes:
> >> On Aug 6, 2018, at 3:27 PM, Tom Lane wrote:
> >> Actually, a concrete reason why that might not be good is that it
> results
> >> in having a single point of failure: once we remove branch N's relnotes
> >> from t
Flavio Henrique Araque Gurgel writes:
> Em ter, 28 de ago de 2018 às 18:21, Tom Lane escreveu:
>> You could as well argue that every single page that describes creating
>> any sort of object ought to repeat this information. I doubt that people
>> would find that to be an improvement.
> I'll ne
Em ter, 28 de ago de 2018 às 18:21, Tom Lane escreveu:
> Flavio Henrique Araque Gurgel writes:
> > It seems that naming prepared statements is limited to 63 characters as
> per
> >
> https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS
>
> Yeah, just like
On 2018-Aug-28, Jonathan S. Katz wrote:
> I have attached patch where I suggested some alternate wording and
> remove the parenthetical comment, as I don’t believe that should be
> an aside.
Cool, thanks. I have pushed it with your proposed wording.
--
Álvaro Herrerahttps://www
