On 2022-Dec-23, Laurenz Albe wrote:
> The example in
> https://www.postgresql.org/docs/current/event-trigger-example.html
> stopped compiling since commit 2f9661311b.
>
> Here is a patch to fix that.
Right, thanks. Applied to all the relevant branches.
--
Álvaro Herrera PostgreSQL De
On 2023-Mar-14, Daniel Gustafsson wrote:
> The docs use PostgreSQL and not Postgres in all but two places, which I think
> we should change like in the attached to be consistent. Any objections to
> this?
Both are very new. No objection to the change.
--
Álvaro HerreraBreisgau, Deutsc
On 2023-May-02, Daniel Gustafsson wrote:
> +
> + LSN
> +
> +
>
> The other entries doesn't have a glossentry id
> attribute set, is the use here related to the glossentry.show.acronym param?
I debated with myself for 347d2b07fcc2 on whether to add id attribs to
entries. The only savi
On 2023-May-18, PG Doc comments form wrote:
> I noticed that range_agg is listed in the Postgres 14 documentation as an
> available aggregate function here:
> https://www.postgresql.org/docs/14/functions-aggregate.html
>
> However, my understanding is that this feature isn't available until
> Pos
On 2023-May-19, Alvaro Herrera wrote:
> On 2023-May-18, PG Doc comments form wrote:
>
> > I noticed that range_agg is listed in the Postgres 14 documentation as an
> > available aggregate function here:
> > https://www.postgresql.org/docs/14/functions-aggregate.h
On 2023-Sep-25, Daniel Gustafsson wrote:
> This does of course present a question for the backbranches, pointing to the
> HEAD version in the docs for a previous major release isn't entirely accurate.
> On the other hand, we already do that today in the above tableam page so if we
> don't like tha
On 2023-Oct-11, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/logical-replication-architecture.html
> Description:
>
> There are dublicated section named "31.7.1. Initial Snapshot" on
> https://www.p
On 2023-Oct-11, David G. Johnston wrote:
> Or move 4 paragraphs of introductory material into its own section so that
> there are two sections and a brief sentence for an intro.
We have lots of other places where this (single-entry TOCs) happens. I
don't think we want to add spurious tags in al
On 2023-Oct-16, PG Doc comments form wrote:
> I'm confused by this paragraph:
>
> > These popular data structures were originally developed for in-memory
> > usage. In main memory, they are usually designed as a set of dynamically
> > allocated nodes linked by pointers. This is not suitable for d
On 2023-Nov-13, Daniel Gustafsson wrote:
> That's a fair point. It's sort of hard to refer back from the acronym list
> though since we don't have a single Access Method section but instead one for
> Indexes and one for Relations. In the attached diff I propose that we add a
> glossary entry for
On 2023-Nov-22, Laurenz Albe wrote:
> I think the example had best be at "8.5.2. Date/Time Output", in
> doc/src/sgml/datatype.sgml around line 2552.
Actually, isn't that a strange location? Chapter 8.5.2 is about the
datatype itself, and there's already a cross-link to Section 9.8 for
to_char()
On 2023-Nov-27, Erik Wienhold wrote:
> Two issues that I fixed in the attached patch:
>
> * it's called "extended format" not "T format" (the "T" is mandatory
> anyway)
+1
> * the time zone was missing from the result output
This is wrong. Actually, there's no timezone in value, because the
On 2023-Nov-27, Nikolay Samokhvalov wrote:
> https://www.postgresql.org/docs/current/ddl-partitioning.html provides an
> example of using CONCURRENTLY for index creation of partitioned tables; but
> it the example itself doesn't have this word; here is a fix:
You're right, my mistake. Will push
On 2023-Nov-29, Tom Lane wrote:
> Eric Hanson writes:
> > The larger point being, the "name" vs "alias" paradigm presented in this
> > table does not accurately represent PostgreSQL, and conveys an inaccurate
> > picture of the relationship between type names. int4 is not an "alias".
>
> I agre
On 2024-Jan-24, Laurenz Albe wrote:
> For months now, I have received this automated reply whenever I post to
> this list:
Yeah, me too -- the oldest I can find is 27th November last year, but
it's quite possible that I deleted older ones without leaving traces.
I unsubscribed this address now, t
On 2024-Jan-24, Laurenz Albe wrote:
> The permissions are transferred to the new owner, so the old owner doesn't
> have any privileges on the object (and, in your case, cannot connect to
> the database any more).
However, if the old owner had a pg_hba.conf line that allowed them in,
and the new o
On 2024-Feb-06, Daniel Gustafsson wrote:
> > On 5 Feb 2024, at 22:23, PG Doc comments form
> > wrote:
>
> > This page has a link that says "See the release notes for PostgreSQL 12 for
> > details on this change."
> > https://www.postgresql.org/docs/current/recovery-config.html
> >
> > The link
On 2024-Mar-06, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/libpq-pipeline-mode.html
> Description:
>
> The calls to PQpipelineSync and PQsendFlushRequest may either report failure
> or success, bu
On 2024-Apr-24, Peter Eisentraut wrote:
> On 24.04.24 10:08, Nicolas Seinlet wrote:
> > It was not crystal clear to me that when wal_recycle is also ON , the
> > recycled files are not filled with zeroes, because they are not
> > considered as new. Could we add a sentence stating this?
>
> It cu
On 2024-Apr-12, Erik Wienhold wrote:
> There's this bug[1] in the DocBook XSLT stylesheets. Looks like the
> fix[2] landed in 1.79.2 (latest version on Arch,
Maybe one of these days we should get going with the migration to
Docbook 5.x that Jürgen Purtz proposed.
https://postgr.es/m/21ed3fd9-90
On 2024-Apr-25, Jürgen Purtz wrote:
> Great recommendation. I may have time in the second half of June to
> pursue the migration further. There is a performance problem, which
> possibly results from our XSLT script that optimizes the
> transformation-speed and works well in 4.x.
Maybe a way to
On 2024-May-05, David Rowley wrote:
> On Sun, 5 May 2024 at 12:41, Erik Wienhold wrote:
> > So, I think we should either remove that one nchar instance (because it
> > doesn't add any real value) or document it properly. The attached patch
> > does the latter.
>
> It seems easier to do the form
By the way, this neighboring sentence is a bit awkward
" It must be ... or a type for which there is a cast from json to that type."
Would it be better to say
" It must be ... or a type to which a cast from json exists."
?
--
Álvaro Herrera 48°01'N 7°57'E — https://www.Enterpr
On 2024-Jun-03, Euler Taveira wrote:
> On Thu, May 30, 2024, at 12:50 PM, PG Doc comments form wrote:
> > I noticed that in "28.4.4. Progress Reporting" chapter for
> > `pg_stat_progress_create_index`, the "Table 28.43. CREATE INDEX Phases" may
> > be misleading as phase displayed for "building i
On 2024-Jun-13, Laurenz Albe wrote:
> On Thu, 2024-06-13 at 08:59 +, PG Doc comments form wrote:
> > Page: https://www.postgresql.org/docs/16/datatype-uuid.html
> > Description:
> >
> > Is this the right sentence? "use of upper-case digits"
> > > > PostgreSQL also accepts the following altern
On 2024-Jul-24, Laurenz Albe wrote:
> Here is a patch for that; it may be the smallest patch I've ever
> written for PostgreSQL.
Thanks, applied.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Investigación es lo que hago cuando no sé lo que estoy haciendo"
(W
On 2024-May-06, Erik Wienhold wrote:
> On 2024-05-06 10:59 +0200, Alvaro Herrera wrote:
> > By the way, this neighboring sentence is a bit awkward
> >
> > " It must be ... or a type for which there is a cast from json to that
> > type."
> Or maybe just
&
Peter Eisentraut wrote:
> The attached patch removes endterm attributes from xref elements and the
> associated id attributes on title elements.
>
> Older documentation toolchains could not automatically generate text for
> xrefs into refentries, so we had to use the endterm attribute to tell it
>
Can we have it emit something like
see section 4.5.3 “Building Indexes Concurrently”
by customizing the stylesheets? I tried to figure out where the text is
emitted, but 'sectioncalled' does not appear in greps anywhere in the
docbooc-xsl dir.
--
Álvaro Herrerahttps://www.2nd
Steve Atkins wrote:
> It's been useful a few times to reassure people that we can handle "large"
> databases operationally, rather than just having large theoretical limits.
>
> Updating it would be great, or wrapping a little more verbiage around the
> 4TB number, but a mild -1 on removing it al
Brian McKiernan wrote:
> My Issue:
> My primary keys in a certain table are not contiguous.
If you have a need to have values that are contiguous, you need to ask
yourself why and then see what mechanism provides the semantics you
need. An easy way is to lock the table containing the column, for
Michael Paquier wrote:
> On Fri, Jan 19, 2018 at 11:33:43AM -0500, Tom Lane wrote:
> > It means reading the whole table and writing it out in some modified
> > form (for instance, with some column transformed into a new datatype).
> > It's not "dangerous" in any way ... but if you've got many GB of
PG Doc comments form wrote:
> create table t(x int);
> create table u(x int);
>
> insert into t values (1), (2), (2), (3), (3);
> insert into u values (1), (2);
>
> select * from t except all select * from u;
> x
> ---
> 3
> 3
> 2
> (3 ro
Peter Eisentraut wrote:
> On 2/26/18 20:02, Craig Ringer wrote:
> > If I were maintaining the docs in a vacuum, I'd use graphviz for
> > something like that, because it's a figure that does need regular
> > updates and changes. And because
> > the list of fun things to do in my life definitely doe
David G. Johnston wrote:
> I'm not seeing the value in providing a link, especially one that we don't
> control, here. Futhermore, we could probably drop the whole "In
> practice..." sentence. But if not at least put a period after "limitation"
> and drop the example and link.
+1 remove the se
PG Doc comments form wrote:
> The documentation says:
>
> For a SELECT or CREATE TABLE AS command, the tag is SELECT rows where rows
> is the number of rows retrieved.
>
> But what I get back from the server is this packet:
>
> 43 00 00 00 11 43 52 45 41 54 45 20 54 41 42 4c CCREATE
Peter Eisentraut wrote:
> On 5/2/18 18:59, Ian Maddox wrote:
> > It appears that the knowledge from that page has been redistributed
> > across the manual in versions 8+, making it difficult to point to a
> > single authoritative resource. I'm writing to request that a single
> > section on securi
Eugene Wang wrote:
> Unique Constraint and Unique Index should be the same in this single-column
> case, right?
>
> Because, according to CONSTRAINT page in Postgres Documentation, Unique
> Constraint on single column is realized as Unique B-TREE index.
>
> I have just realized that it is still a
On 2018-May-30, Michael Paquier wrote:
> > ClientRead Waiting to read data from the client.
> > ClientWrite Waiting to write data from the client.
> > ...
> > ^
> > It should state TO CLIENT.
>
> Good catch. It seems that this is my fault as what has been d
On 2018-May-30, Michael Paquier wrote:
> On Wed, May 30, 2018 at 01:30:08PM -0400, Alvaro Herrera wrote:
> > I do not think that patch does what you think it does.
>
> Oops. Sorry another patch got on the way. Here you go.
Okay, pushed. Because of the sgml to xml conversion,
On 2017-Sep-11, Daniel Gustafsson wrote:
> When reviewing Pavels patch for default namespace in XMLTABLE, I came across
> this sentence in the devel (and 10beta) docs in subsection 9.14.3.3. xmltable:
>
> The following example illustrates how the XMLNAMESPACES clause can be
> used to
When doing a test run of the PDF docs for beta2 on borka, I noticed that the
build finishes with this -- is it expected?
[WARN] FOUserAgent - Destination: Unresolved ID reference
"ecpg-type-timestamp-date" found.
[WARN] FOUserAgent - Destination: Unresolved ID reference
"sql-altercollation-notes
On 2018-Jul-02, Michael Paquier wrote:
> Here are all the broken links in the source tree:
>
> doc/src/sgml/libpq.sgml:
> Wrong: http://h71000.www7.hp.com/doc/83final/ba554_90007/ch04.html
> Correct: http://h41379.www4.hpe.com/doc/83final/ba554_90007/ch04.html
>
> doc/src/sgml/runtime.sgml:
>
On 2018-Aug-06, Tom Lane wrote:
> OTOH, if we can easily set up a generic redirect rule like "if
> https://www.postgresql.org/docs/*/static/release-*.html
> doesn't exist, then redirect to
> https://www.postgresql.org/docs/old-release-notes/static/release-*.html";
> it might be worth doing.
Yeah
Hello
A customer of ours was taken by surprise by a change in Postgres 10 on a
trial upgrade from 9.6. They were using sequences from SERIAL columns a
little unorthodoxly, and their stuff stopped working: essentially, they
hacked the default expression so that it'd automatically use negative
numb
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
On 2018-Sep-27, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/10/static/runtime-config-autovacuum.html
>
> This page lists the different autovacuum options. Describing
> autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor independently
> adds confusion unless you
On 2018-Oct-04, Pavel Stehule wrote:
> čt 4. 10. 2018 v 17:50 odesílatel Jonathan S. Katz
> napsal:
>
> When I am going to document, then I see (about 0.5 sec) big PostgreSQL
> logo. It is not pleasant effect.
>
> I don't like table style - middle vertical line is too black
>
> Used colour pal
On 2018-Oct-22, Liudmila Mantrova wrote:
> I have noticed a small rendering issue in the Chrome browser. If you follow
> a link to a bookmark in a different page, it's hidden below the website
> header. Links within the same page and section-level links appear to work
> fine.
Yeah, I see this eff
On 2018-Nov-05, Bruce Momjian wrote:
> Well, here are the lines in guc.c:
>
> gettext_noop("Sets the planner's assumption about the size of the
> data cache."),
> gettext_noop("That is, the size of the cache used for PostgreSQL
> data files. "
>
On 2018-Aug-17, Thomas Munro wrote:
> On Fri, Aug 17, 2018 at 1:12 PM, Justin Pryzby wrote:
> > I dearly hope this was intentional ;)
> >
> > commit 96e98fa2606b2b12805db99196f468152312af14
> > Author: Thomas Munro
> > Date: Fri Aug 17 11:32:55 2018 +1200
> >
> > Proof-reading for documen
On 2018-Nov-20, Jonathan S. Katz wrote:
> On 11/19/18 9:05 PM, Bruce Momjian wrote:
> > On Tue, Oct 23, 2018 at 06:29:55PM +, PG Doc comments form wrote:
> >> The following documentation comment has been logged on the website:
> >>
> >> Page: https://www.postgresql.org/docs/11/static/indexes-u
On 2018-Nov-20, Tom Lane wrote:
> So what I think I should do is reformulate that discussion to talk
> about making covering indexes with INCLUDE, and then mention in
> passing that you can also do it without that as long as you don't mind
> the payload columns being part of the index semantics.
On 2018-Nov-28, Bruce Momjian wrote:
> On Wed, Nov 28, 2018 at 11:46:33AM -0800, Andres Freund wrote:
> > Hi,
> >
> > On 2018-11-28 18:34:26 +0100, Jürgen Purtz wrote:
> > > After one week no response at all? Neither positive nor negative. It seems
> > > that the community has little interest in
On 2018-Dec-07, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.4/external-pl.html
> Description:
>
> At https://www.postgresql.org/docs/9.4/external-pl.html, the link to PL/Py
> is broken. Specifically
On 2018-Dec-07, Alvaro Herrera wrote:
> On 2018-Dec-07, PG Doc comments form wrote:
>
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/9.4/external-pl.html
> > Description:
> >
> &
On 2018-Nov-04, Erik Rijkers wrote:
> I wouldn't mind if this page:
> https://www.postgresql.org/community/contributors/
>
> contained a link to (contributors v11):
> https://www.postgresql.org/docs/11/static/release-11.html#id-1.11.6.5.6
>
> and to (contributors v10)
> https://www.postgresql.
On 2018-Dec-21, Tom Lane wrote:
> Alvaro Herrera writes:
> > I propose the following patch, which will make those links stable --
> > then we can add the following links to the contributors page:
> > https://www.postgresql/org/docs/10/release-10.html#RELEASE-10-ACKNO
On 2019-Jan-01, PG Doc comments form wrote:
> This line:
> The user's client (frontend) application that wants to perform database
> operations.
> in the Architecture
> Fundamentals(https://www.postgresql.org/docs/10/tutorial-arch.html) seems
> out of place or incomplete.
How so? It's part of th
On 2019-Jan-17, Magnus Hagander wrote:
> Per the docs comment today, I will remove the notes about majordomo at
> https://www.postgresql.org/docs/current/bug-reporting.html.
>
> However, this one also suggests email to the pgsql-bugs report as the
> primary choice "and you can also use the bugs f
On 2018-Dec-23, Jürgen Purtz wrote:
> b) Is it worth to visualize PG's tree-implementation in a separate graphic -
> or is it the same as in every other tree-implementation that you have
> learned in your academic studies? If yes: in which chapter?
Who's to say that every single reader of the PG
On 2018-Dec-27, Magnus Hagander wrote:
> On Fri, Dec 21, 2018 at 4:17 PM Alvaro Herrera
> wrote:
>
> > On 2018-Dec-21, Tom Lane wrote:
> >
> > > Alvaro Herrera writes:
> > > > I propose the following patch, which will make those links stable --
>
On 2019-Feb-04, Andres Freund wrote:
> Gah, I'd skipped this thread, because I was OK, if not happy, about the
> original modest proposal (trimming to supported versions). My fault.
>
> For the record: I think this is a terrible idea.
+1 I don't like it either. The original idea of just removi
I think we should first exhaust all options to use the currently
supported formats, before adding a new controversial one. You can use
the {s} qualifier for a box in ditaa and it'll show a disk; this ascii
diagram produces a "similar enough" image to your diagram, for example:
++
On 2019-Apr-10, Fujii Masao wrote:
> Hi,
>
> I'd like to propose to mark reloptions as indexterms, like GUC,
> so that users can more easily search the pages describing
> a reloption in document. Attached is the patch which does this.
> Is this helpful? Thought?
+1 for adding index entries to al
On 2019-Apr-12, Fujii Masao wrote:
> On Wed, Apr 10, 2019 at 4:11 AM Alvaro Herrera
> wrote:
> >
> > On 2019-Apr-10, Fujii Masao wrote:
> >
> > > Hi,
> > >
> > > I'd like to propose to mark reloptions as indexterms, like GUC,
> &g
On 2019-Apr-12, Michael Paquier wrote:
> On Fri, Apr 12, 2019 at 12:33:45PM +0900, Fujii Masao wrote:
> > Indeed. Attached is the updated version of the patch.
>
> On top of what Alvaro has mentioned, it seems to me that we should
> make the difference between table-level configuration parameter
On 2019-Apr-12, Fujii Masao wrote:
> OTOH, originally I thought that the following style is smarter.
>
> xxx
> configuration parameter, XXX
> storage parameter, Storage Parameter
Ah. Well, I like this style. Let's do that.
--
Álvaro Herrerahttps://www.2nd
On 2019-Apr-16, Fujii Masao wrote:
> On Sat, Apr 13, 2019 at 1:30 AM Alvaro Herrera
> wrote:
> >
> > On 2019-Apr-12, Fujii Masao wrote:
> >
> >
> > > OTOH, originally I thought that the following style is smarter.
> > >
> >
On 2019-Apr-16, Fujii Masao wrote:
> On Tue, Apr 16, 2019 at 12:35 AM Alvaro Herrera
> wrote:
> > For autovacuum it says "configuration
> > parameters" rather than "configuration parameter". Other than that, it
> > looks good to me. (I didn&#
On 2019-Apr-26, Tom Lane wrote:
> We appear to have a fair amount of support now for operations like
> constructing a partitioned index piecemeal, e.g. adding indexes
> to the partitions one at a time and then attaching them to a
> parent partitioned index, with the parent ultimately transitioning
On 2019-May-09, Bruce Momjian wrote:
> On Wed, May 8, 2019 at 07:40:16AM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/10/install-short.html
> > Description:
> >
> > 1)
> > $ mkdir /usr/lo
On 2019-Apr-26, Tom Lane wrote:
> Alvaro Herrera writes:
> > I suppose I better add something in Chapter 5 (DDL), possibly inside the
> > 5.10 section (Table Partitioning) -- a new 5.10.6 "Indexes for
> > Partitioned Tables" perhaps?
>
> I was expecti
On 2019-May-16, Alvaro Herrera wrote:
> On 2019-Apr-26, Tom Lane wrote:
>
> > Alvaro Herrera writes:
> > > I suppose I better add something in Chapter 5 (DDL), possibly inside the
> > > 5.10 section (Table Partitioning) -- a new 5.10.6 "Indexes for
> >
On 2019-Jun-13, Pavel Luzanov wrote:
> Hello,
>
> According to patch[1] and after playing with v12 beta1 I think that this
> item can be dropped from "5.11.3. Implementation Using Inheritance" section
> of v12 docs:
>
> "Some operations require a stronger lock when using declarative partitioning
On 2019-Jul-02, Daniel Gustafsson wrote:
> > On 2 Jul 2019, at 10:13, Jürgen Purtz wrote:
>
> > The alternative is a downshift of the postings by one level, see attachment
> > 2. How to realize this behavior is shown in attachment 3.
>
> This alternative seems a better idea.
I agree -- the ot
On 2019-Jul-09, Amit Langote wrote:
> As mentioned in the docs, defining exclusion constraints on
> partitioned tables is not supported.
Right.
> "While defining a primary key and unique constraints on partitioned
> tables is supported, the set of columns being constrained must include
> all of
On 2019-Jul-25, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/plpgsql-expressions.html
> Description:
>
> In section 43.4, in the sentence "(...) and then this prepared statement is
> EXECUTEd (...)"
On 2019-Jul-19, Jürgen Purtz wrote:
> This is an adoption of the genetic-algorithm.gv file to the style of the
> gin.gv file: same font, similar header, use of TAB instead of SPACE.
I pushed this with trivial changes, thanks.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
Postgre
On 2019-Aug-30, Tom Lane wrote:
>
>
>
>
>Reserve a range of OIDs (9000-) to be used for external
>extensions (Andres Freund)
>
>
>
> This seems more or less completely misleading.
Hmm. I wonder if this item really belongs in the release notes at a
On 2019-Sep-02, Jürgen Purtz wrote:
> We plan to integrate figures into version 12. Currently there are 2 resp. 3
> figures in git (BETA3 / master). This may be intended - or not. Additionally
> there are some patches in the mailing list.
I purposefully pushed that figure to master only; pg12 is
On 2019-Sep-11, Pavlo Golub wrote:
> Trying to view
>
> https://www.postgresql.org/docs/11/auth-methods.html
> https://www.postgresql.org/docs/12/auth-methods.html
> https://www.postgresql.org/docs/current/auth-methods.html
>
> gives me an empty page. Previous versions are not affected.
That's
On 2019-Aug-30, Bruce Momjian wrote:
> OK, how is this patch? I didn't mention psql since I think everyone
> expects psql to show all information about tables and indexes.
Why would you change perform.sgml? It seems unnecessary; the commands
shown work fine.
This part seems okay:
> diff --git
On 2019-Sep-12, Alexander Korotkov wrote:
> On Thu, Sep 12, 2019 at 4:58 PM Liudmila Mantrova
> wrote:
> > Please consider these small patches for REL_12_STABLE that mainly fix
> > remaining typos and some tagging issues. The jsonpath-related one also
> > improves some wordings, e.g. there see
On 2019-Sep-26, Bruce Momjian wrote:
> On Wed, Sep 11, 2019 at 06:15:22PM -0300, Alvaro Herrera wrote:
> > On 2019-Aug-30, Bruce Momjian wrote:
> >
> > > OK, how is this patch? I didn't mention psql since I think everyone
> > > expects psql to show al
On 2019-Nov-06, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/12/ddl-alter.html
> Description:
>
> In 5.6.1. Adding a Column, there is a kind of example 'ALTER TABLE products
> ADD COLUMN description text;'
>
> The words 'description' and 'text' are misleading -- as accordi
On 2019-Nov-07, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/12/manage-ag-templatedbs.html
> Description:
>
> The use of the word virgin as an adjective is incorrect here and also an
> anachronism. It is better off replaced with the word pristine - quotes
> unnecessary. Not
On 2019-Nov-07, Bruce Momjian wrote:
> On Thu, Nov 7, 2019 at 07:55:22PM +0100, Daniel Gustafsson wrote:
> > > On 7 Nov 2019, at 16:03, Alvaro Herrera wrote:
> > > We could say "empty", which seems better suited than both "virgin" and
> > >
Remote DBA, Training & Services
>From b394a1b2b6227d68e0cd2c32afb75ef3bfd317ef Mon Sep 17 00:00:00 2001
From: Alvaro Herrera
Date: Fri, 8 Nov 2019 10:09:05 -0300
Subject: [PATCH] No more virgins
---
doc/src/sgml/manage-ag.sgml | 5 +++--
doc/src/sgml/ref/create_database.sgm
On 2019-Nov-08, Tom Lane wrote:
> Alvaro Herrera writes:
> > Here's a proposed patch.
>
> I don't like this wording much, because "no user-defined objects"
> is not a sufficient specification of what we are talking about.
> You need to also cap
On 2019-Nov-08, Tom Lane wrote:
> Alvaro Herrera writes:
> > Hmm. Maybe we can say "pristine database" and then add this explanation
> > in a parenthical comment:
>
> > This is particularly handy when restoring a
> > pg_dump dump:
On 2019-Nov-08, Tom Lane wrote:
> Alvaro Herrera writes:
> > On 2019-Nov-08, Tom Lane wrote:
> >> So the patch becomes s/virgin/pristine/g plus add a parenthetical
> >> definition for the first use? Works for me.
>
> > Well, there are three uses of
On 2019-Nov-25, Daniel Gustafsson wrote:
> > On 25 Nov 2019, at 13:05, PG Doc comments form
> > wrote:
> > Examples should have specified 'english'.
> >
> > Instead:
> > to_tsvector('fat cats ate rats') @@ to_tsquery('cat & rat')
> >
> > which returns fale on my own blank installation of Po
On 2019-Nov-27, Daniel Gustafsson wrote:
> > On 26 Nov 2019, at 19:28, Alvaro Herrera wrote:
>
> > Or perhaps we can add a second line in the example cell for the
> > @@ operator, to make it clear that both forms can be used. Users can be
> > expected to apply som
On 2019-Dec-19, Tom Lane wrote:
> I wrote:
> > Concretely, I propose the attached. Anybody want to editorialize on
> > my short descriptions of the auth methods?
>
> Pushed after a bit more fiddling with the wording.
Looks good, thanks.
--
Álvaro Herrerahttps://www.2ndQuadrant
On 2020-Jan-02, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/sql-createtable.html
> Description:
>
> From 73ad66d721a3f87500857cdc6b1f4d810f2875df Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Ivan=20M
Hi,
On 2020-Jan-02, helix84 wrote:
> Hi, I prefer to bookmark docs pointing to the exact term I need and
> with pg docs it's often been the case that the exact term doesn't have
> an anchor or only has unstable, generated anchors. So I would very
> much like to add stable anchors in many more pla
On 2020-Feb-03, Jonathan S. Katz wrote:
> So, if there was something done to redirect people from specific
> deprecated documentation pages historically, it was before my time. Most
> of the redirects have been as general purposes ones (e.g. /docs/12), the
> rules we put in for getting rid of "sta
On 2020-Feb-12, Tom Lane wrote:
> For amusement's sake, attached is a screenshot of what Table 9-33
> looks like in A4 format, with my one-row-per-example patch of
> yesterday plus a few manually-added zero-width spaces to break up
> the examples. This is the first PDF rendering of that table tha
On 2020-Feb-12, Tom Lane wrote:
> With a separate argument-types cell it'd likely be
> better to just leave the cell empty, but do we want to write
> just "→ rettype" in a signature cell?
Yeah, it'd look very odd, and certainly the no-parens case makes it
worse. I like this end result:
> so bei
1 - 100 of 190 matches
Mail list logo
