Re: [DOCS] Questionable tag usage

eforge.net/html/en/dbc.markup.xref-vs-link.html Eh, we use both and for internal links and surely want both to be validated. If that's no longer happening I don't think it will be long before it bites us. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- S

Re: [DOCS] [HACKERS] Questionable tag usage

I won't lose a lot of sleep over it if we decide to go that direction, though. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] [HACKERS] Questionable tag usage

On Tue, Jan 10, 2017 at 10:58 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> On Fri, Jan 6, 2017 at 10:18 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >>>> I don't think there are a lto of people who use dead tree editi

Re: [DOCS] [HACKERS] Questionable tag usage

er > you have to mouse over it to find out that it would take you somewhere. > Not sure if that's enough of a usability fail to argue for keeping the > old way. Personally, I wouldn't sweat it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Re: [DOCS] monitoring.sgml - clarify length of query text displayed in pg_stat_statements

stat_statements documentation, but it looks correct, so I have committed it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Description tweak for vacuumdb

o me that we could probably tweak the phrasing here so that a non-clueful person wouldn't go astray. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [HACKERS] [DOCS] max_worker_processes on the standby

On Wed, Dec 9, 2015 at 4:21 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Robert Haas wrote: >> On Mon, Dec 7, 2015 at 8:33 AM, Fujii Masao <masao.fu...@gmail.com> wrote: > >> > So firstly you will push those "latest" changes soon? >> >&

Re: [HACKERS] [DOCS] max_worker_processes on the standby

- >> | 630 | fg >> (1 fila) >> >> Not sure what is going on; my reading of the code certainly says that >> the data should be there. I'm looking into it. >> >> I also noticed that I didn't actually push the whole of the patch >> yesterday -- I neglected

Re: [HACKERS] [DOCS] max_worker_processes on the standby

erver. > Committs is activated in the standby because track_commit_timestamp is > enabled. This seems wrong already at this point. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)

Re: [HACKERS] [DOCS] max_worker_processes on the standby

All the checks inside the commit_ts code were changed > to use this new variable. I also removed the static variable Alvaro added in > previous commit because it's not needed anymore. That sounds good to me. On a quick read-through it looks OK too. -- Robert Haas EnterpriseDB: http://www.ente

Re: [DOCS] max_worker_processes on the standby

standby can have the feature enabled even though the master has it disabled? That seems like it can only lead to heartache. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes

Re: [DOCS] max_worker_processes on the standby

On Fri, Oct 2, 2015 at 2:59 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Robert Haas wrote: >> The standby can have the feature enabled even though the master has it >> disabled? That seems like it can only lead to heartache. > > Can you elaborate? Sort of.

Re: [DOCS] max_worker_processes on the standby

there after promotion, because the DBA might have flipped the switch on and off at different times. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription

Re: [DOCS] max_worker_processes on the standby

On Tue, Aug 4, 2015 at 12:41 AM, Alvaro Herrera alvhe...@2ndquadrant.com wrote: Robert Haas wrote: On Thu, Jul 16, 2015 at 12:07 AM, Fujii Masao masao.fu...@gmail.com wrote: One example which makes me a bit confusing is; both master and standby are running fine with track_commit_timestamp

Re: [DOCS] max_worker_processes on the standby

is not the same between master and standby. Simple question is; why do we need to cause the standby fail in this case? Since I'm not familiar with the code of track_commit_timestamp yet, I'm not sure whether this behavior is valid or not. Hmm, that seems like awfully weird behavior. -- Robert Haas

Re: [DOCS] bgworker / SPI docs patches

, I note that worker_spi doesn't memset(0) its BackgroundWorker struct, so any uninitialized fields will contain garbage. Including bgw_library_name and bgw_function_name. That seems bad. Yeah, that stuff is bad. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL

Re: [DOCS] bgworker / SPI docs patches

the docs build fail unless 0001 is applied first, so I can't pursue that unless you want to revise that accordingly. I've committed 0003, and will look at 0004 next. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list

Re: [DOCS] bgworker / SPI docs patches

On Wed, Jul 29, 2015 at 11:35 AM, Robert Haas robertmh...@gmail.com wrote: On Tue, Feb 17, 2015 at 3:29 AM, Craig Ringer cr...@2ndquadrant.com wrote: After spending a while working on the BDR extension I've found that the current documentation on the SPI and bgworkers could use some more detail

Re: [DOCS] Add link to partial unique index from Constraints (5.3)

can be used to enforce uniqueness in a way other constraints cannot provide. Currently, it not easy to find this type of constraint as not a lot of people would read through documentation on indexes when looking for constraints. I think adding something to that chapter would be good. -- Robert

Re: [DOCS] Call for GIST/GIN/SP-GIST opclass documentation

http://www.postgresql.org/docs/devel/static/gin-builtin-opclasses.html http://www.postgresql.org/docs/devel/static/spgist-builtin-opclasses.html We never had any well-defined place to discuss such opclasses before, but I think it's past time we did. +1. Great idea. -- Robert Haas EnterpriseDB

Re: [DOCS] [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)

output in all the branches. Sounds OK to me. If there's as many as two people using those files, I'll be surprised. (Of course, I've been surprised before.) -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs

[DOCS] Re: Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)

, because who cares? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] Re: Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)

On Tue, Feb 4, 2014 at 1:38 AM, Tom Lane t...@sss.pgh.pa.us wrote: Noah Misch n...@leadboat.com writes: Robert Haas robertmh...@gmail.com writes: I wonder if these standalone things are really worthwhile. I wonder how difficult it would be to make sufficient link data available when

Re: [DOCS] CREATE USER

may be removed in a future release, assuming we want to eventually remove it. But I don't think warning people that CREATEUSER means SUPERUSER and not CREATEROLE is very helpful. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs

Re: [DOCS] Date/Time Types : internals

, even for years before that calendar was in use. /para So which calendar are we using, Julian or Gregorian? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your

Re: [DOCS] separate Privileges section for SQL reference pages?

improvement. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Idea on indexes

it? The current link is exactly where I'd expect it to be. I don't think there's a problem here; not everything can be made prominent. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes

Re: [DOCS] [COMMITTERS] pgsql: Update docs on numeric storage requirements.

On Thu, Mar 22, 2012 at 10:36 PM, Fujii Masao masao.fu...@gmail.com wrote: On Fri, Mar 23, 2012 at 11:12 AM, Robert Haas robertmh...@gmail.com wrote: On Thu, Mar 22, 2012 at 9:21 PM, Fujii Masao masao.fu...@gmail.com wrote: On Fri, Mar 23, 2012 at 4:41 AM, Robert Haas rh...@postgresql.org wrote

Re: [DOCS] NUMERIC size

is three, five or eight for now. Attached patch fixes this. Nice catch. Committed. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http

Re: [DOCS] [PATCH] Use idiomatic style for varlena structs

first pass over the concepts. Definitely; if anything, that's why I was favoring vl_len_. This is a magic field. Do not touch the magic. I've committed the parts of this to which Tom did not object. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Re: [DOCS] PQconninfoParse()

On Tue, Oct 18, 2011 at 8:27 PM, Tom Lane t...@sss.pgh.pa.us wrote: Robert Haas robertmh...@gmail.com writes: On Sat, Oct 15, 2011 at 11:24 AM, Tom Lane t...@sss.pgh.pa.us wrote: Uh, is that actually a true statement?  I thought the result *did* include default values.  That's more or less

Re: [DOCS] [COMMITTERS] pgsql: Update docs on numeric storage requirements.

On Thu, Mar 22, 2012 at 9:21 PM, Fujii Masao masao.fu...@gmail.com wrote: On Fri, Mar 23, 2012 at 4:41 AM, Robert Haas rh...@postgresql.org wrote: Update docs on numeric storage requirements. Since 9.1, the minimum overhead is three bytes, not five. Thanks for the commit! I think that it's

Re: [DOCS] Update documentation wrt visibility map/index-only scans

, as I couldn't figure out how to build docs on my system) Committed after some editing and markup repair. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your

Re: [DOCS] Cannot build docs on Ubuntu 10.04?

docbook-dsssl? It must contain that script. Per prior email, I needed to do a make distclean and re-configure. So do we have a complete list of the packages needed on Ubuntu now, that we could add to the documentation? I grow weary of figuring this out every time I set up a new machine. -- Robert

Re: [DOCS] Bug

, but I wish we had a way. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] docs update for count(*) and index-only scans

. I think it's still more pessimistic than is warranted, but I wasn't sure exactly how to rephrase it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription

Re: [DOCS] docs update for count(*) and index-only scans

them. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Link to PAM pages broken

not sure what we can do. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] PQconninfoParse()

On Sat, Oct 15, 2011 at 11:24 AM, Tom Lane t...@sss.pgh.pa.us wrote: Robert Haas robertmh...@gmail.com writes: Maybe we should change this: Note that only options explicitly specified in the string will have values set in the result array; no defaults are inserted. To say something like

Re: [DOCS] description of CHECKPOINT command confusing

On Fri, Oct 14, 2011 at 1:17 AM, Fujii Masao masao.fu...@gmail.com wrote: Slightly updated patch attached. Looks good. Committed. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org

Re: [DOCS] PQconninfoParse()

On Mon, Oct 10, 2011 at 1:31 PM, Dmitriy Igrishin dmit...@gmail.com wrote: Hey Robert, 2011/10/10 Robert Haas robertmh...@gmail.com On Tue, Sep 27, 2011 at 9:13 AM, Dmitriy Igrishin dmit...@gmail.com wrote: First, Returns parsed connection options from the provided connection string

Re: [DOCS] DROP TABLE can be issued by schema owner as well as table owner

On Fri, Oct 14, 2011 at 11:11 AM, Bruce Momjian br...@momjian.us wrote: Robert Haas wrote: On Thu, Oct 13, 2011 at 10:06 AM, Bruce Momjian br...@momjian.us wrote: I applied the following documentation patch to clarify this issue, and used generic wording user with the proper permissions

Re: [DOCS] DROP TABLE can be issued by schema owner as well as table owner

On Thu, Oct 13, 2011 at 10:06 AM, Bruce Momjian br...@momjian.us wrote: I applied the following documentation patch to clarify this issue, and used generic wording user with the proper permissions. That doesn't seem like an improvement; what permissions are proper? -- Robert Haas EnterpriseDB

Re: [DOCS] Discrepancy in 9.1 Documentation on CREATE ROLE

On Wed, Oct 12, 2011 at 12:59 AM, Tom Lane t...@sss.pgh.pa.us wrote: Robert Haas robertmh...@gmail.com writes: On Tue, Oct 11, 2011 at 11:59 AM, Tom Lane t...@sss.pgh.pa.us wrote: I think removing them from the docs but continuing to accept them makes sense.  We do still hear from people

Re: [DOCS] Document DELETE/UPDATE command tag vs triggers

On Wed, Oct 12, 2011 at 4:39 AM, Marti Raudsepp ma...@juffo.org wrote: On Mon, Oct 10, 2011 at 19:58, Robert Haas robertmh...@gmail.com wrote: Committed. Thanks! Do you think it should be backported to earlier versions too? As it stands, the documentation is misleading. Well, I committed

Re: [DOCS] Document DELETE/UPDATE command tag vs triggers

On Wed, Oct 12, 2011 at 2:27 PM, Marti Raudsepp ma...@juffo.org wrote: On Wed, Oct 12, 2011 at 19:48, Robert Haas robertmh...@gmail.com wrote: Well, I committed about five doc patches that day, and I had to decide for each one whether it was worth back-patching, I decided against back

Re: [DOCS] Document DELETE/UPDATE command tag vs triggers

. The categories, or topics, are editable: click on the CommitFest Topics link near the top-right corner, next to the New Patch link. Then New Topic. Committed. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql

Re: [DOCS] PQconninfoParse()

be specified in the documentation becase the name of the function mismatches its behaviour. What do you mean by all options? Where else are they coming from besides the connection string? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql

Re: [DOCS] Add pg_resetxlog into the index in the document

On Wed, Oct 5, 2011 at 11:03 AM, Fujii Masao masao.fu...@gmail.com wrote: It's helpful to add pg_resetxlog into the index in the document. Patch attached. Committed. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing

Re: [DOCS] typo on libpq.sgml

        /listitem        /varlistentry Fixed, thanks for the report. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [DOCS] lo_manage trigger on updates

. Patch? :-) -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Small correction in http://www.postgresql.org/docs/9.0/interactive/wal-reliability.html

can be queried using command camcontrol identify/command, and the write cache both queried and changed using commandsdparm/command when available. Done, in master and REL9_1_STABLE. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs

Re: [DOCS] Discrepancy in 9.1 Documentation on CREATE ROLE

separate command CREATE USER. See http://www.postgresql.org/docs/9.1/static/sql-createuser.html I wonder if we ought to consider removing CREATEUSER and NOCREATEUSER as synonyms for SUPERUSER and NOSUPERUSER. It looks like that change was made in 8.1, which is now EOL. -- Robert Haas EnterpriseDB

Re: [DOCS] create foreign table

? like this: Home - Documentation - Manuals - PostgreSQL 9.1 - I. SQL Commands That's not a bad idea either. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your

Re: [DOCS] 5.3.5. Foreign Keys (The SQL Language) possible enhance

On Sun, Sep 11, 2011 at 9:09 PM, Bruce Momjian br...@momjian.us wrote: Robert Haas wrote: On Fri, May 6, 2011 at 9:50 PM, Grzegorz Szpetkowski gszpetkow...@gmail.com wrote: I have some remark about Now it is impossible to create orders with product_no entries that do not appear

Re: [DOCS] documenting contrib modules (was Re: Building PDFs error)

On Mon, Sep 5, 2011 at 2:08 PM, Bruce Momjian br...@momjian.us wrote: Is this a TODO? Well, it's on my personal TODO list to wear down Tom's resistance to the idea. But I'm not sure we have any project-wide consensus on it at this point. -- Robert Haas EnterpriseDB: http

Re: [DOCS] create foreign table

document the meaning of server_name, which I think is probably what you were after. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http

Re: [DOCS] Building PDFs error: \pdfendlink ended up in different nesting level than \pd

. Is this a TODO?  Did we ever decide on this? Well, some of the contrib modules are such little stupid things that giving them their own chapter seems excessive. sepgsql might merit its own chapter, but dummy_seclabel surely doesn't. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com

Re: [DOCS] postgres-9.1beta3 typo: recommendable -- recommended

database. probably it is refering to the user's resources... maybe we can make it more explicit? The only thing that seems weird about it to me is that recommendable is a word that is almost never used by native English speakers. Or at least not the native English speakers I know. -- Robert Haas

Re: [DOCS] psql's ON_ERROR_STOP is misdocumented

On Tue, Jun 14, 2011 at 11:14 AM, Tom Lane t...@sss.pgh.pa.us wrote: Robert Haas robertmh...@gmail.com writes: Hearing no objections, committed. Looking at this a second time, it needs spell-checked.  variale? Picky, picky. You say potato, I say potatoe. -- Robert Haas EnterpriseDB: http

Re: [DOCS] Documentation and explanatory diagrams

with the proper editor. Or at least, somebody passes it through the proper editor before committing.  As long as said editor can read SVG output from a reasonable range of other tools, this doesn't seem that onerous. Bad news, Bruce: you're going to have to learn a new tool. :-) -- Robert

Re: [DOCS] Information about WAL Configuration needs an update

On Mon, Jun 13, 2011 at 2:25 PM, Rafael Martinez r.m.guerr...@usit.uio.no wrote: On Mon, 2011-06-13 at 13:24 -0400, Robert Haas wrote: On Fri, Jun 3, 2011 at 3:42 AM, Rafael Martinez You can see the graph with the generation of WAL files + some extra information for this test here: http

Re: [DOCS] [COMMITTERS] pgsql: More foreign table documentation improvements.

On Mon, Jun 13, 2011 at 9:56 AM, Fujii Masao masao.fu...@gmail.com wrote: On Mon, Jun 13, 2011 at 9:30 PM, Robert Haas rh...@postgresql.org wrote: More foreign table documentation improvements. Shigeru Hanada, with some additional wordsmithing by me This commit caused the following error

Re: [DOCS] Missing doc for operator args in alter extension

On Thu, Apr 7, 2011 at 9:49 PM, Tom Lane t...@sss.pgh.pa.us wrote: Robert Haas robertmh...@gmail.com writes: On Mon, Apr 4, 2011 at 9:10 PM, Daniele Varrazzo daniele.varra...@gmail.com wrote: the documentation for ALTER EXTENSION is missing the description for the arguments of the form ADD

Re: [DOCS] psql's ON_ERROR_STOP is misdocumented

=# Can we get the docs changed to reflect reality? Here's an attempt at some suitable word-smithing. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company on-error-stop.patch Description: Binary data -- Sent via pgsql-docs mailing list (pgsql-docs

Re: [DOCS] 7.2. Table Expressions FULL join is only supported with merge-joinable join conditions

for exactly what is needed. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Improve warnings around CREATE INDEX CONCURRENTLY

for +    them to complete. Alvaro, did you commit this? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Add link to current_schemas in config.sgml

. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Add link to current_schemas in config.sgml

On Mon, Jun 13, 2011 at 12:55 PM, Brendan Jurd dire...@gmail.com wrote: On 14 June 2011 02:39, Robert Haas robertmh...@gmail.com wrote: On Tue, May 31, 2011 at 2:27 AM, Brendan Jurd dire...@gmail.com wrote: This is just a quick docs patch to add a link to the mention of the current_schemas

Re: [DOCS] 7.2. Table Expressions suggestion about NATURAL JOIN

something like: Note that if there is no any shared column between tables, then NATURAL JOIN acts like ON TRUE (that is, tables are cross-joined), because it's not obvious. Done, with different wording. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Re: [DOCS] Add link to current_schemas in config.sgml

On Mon, Jun 13, 2011 at 1:01 PM, Brendan Jurd dire...@gmail.com wrote: On 14 June 2011 02:58, Robert Haas robertmh...@gmail.com wrote: On Mon, Jun 13, 2011 at 12:55 PM, Brendan Jurd dire...@gmail.com wrote: On 14 June 2011 02:39, Robert Haas robertmh...@gmail.com wrote: On Tue, May 31, 2011

Re: [DOCS] Information about WAL Configuration needs an update

no upper bound. I don't think we have any kind of hard stop where, if no log space is available, we just refuse to process write transactions - such a thing would seem to be rather dangerous. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql

[DOCS] Re: [BUGS] BUG #5926: information schema dtd_identifier for element_types, columns, parameters views inconsistent

On Wed, May 25, 2011 at 7:29 AM, Susanne Ebrecht susa...@2ndquadrant.com wrote: I think we should fix the documentation here. Patch? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org

Re: [DOCS] [HACKERS] DOCS: SGML identifier may not exceed 44 characters

release 3 (Taroon Update 9), and docbook.dcl is from the docbook-dtds-1.0-17.2 RPM. Maybe that really only affects quite old versions, but I think it wouldn't hurt to shorten the tag in question to avoid the problem. +1. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise

Re: [DOCS] createuser/dropuser username

CREATE ROLE is not), which I think is not fully known and is undocumented here. For example: I'm not sure this really needs to be documented, but what exactly do you have in mind? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs

Re: [DOCS] 5.3.5. Foreign Keys (The SQL Language) possible enhance

REFERENCES products (product_no) NOT NULL,    quantity integer ); I don't think we should change the example, but we could probably clarify the wording. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs

Re: [DOCS] ALTER TABLE doc small thing

, but rather confusing and effectively do nothing (maybe just impression purpose). I guess we could remove it, but I don't think it's really doing any harm. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs

Re: [DOCS] [HACKERS] Uppercase SGML entity declarations

On Tue, Apr 5, 2011 at 6:55 PM, Josh Kupershmidt schmi...@gmail.com wrote: On Mon, Apr 4, 2011 at 3:02 PM, Robert Haas robertmh...@gmail.com wrote:  In theory, we have documentation that explains this: http://www.postgresql.org/docs/current/static/docguide-toolsets.html While we're

Re: [DOCS] Add strftime escapes to Log config

On Tue, Mar 29, 2011 at 2:53 PM, Josh Berkus j...@agliodbs.com wrote: We could also link to http://pubs.opengroup.org/onlinepubs/007908799/xsh/strftime.html, for example. That would be helpful.  I still think we want a few examples in our docs, though. Patch? -- Robert Haas EnterpriseDB

Re: [DOCS] number of semaphores and semaphore sets

that nothing material has changed here since 8.3, so I'm inclined to back-patch this doc fix back that far. Barring objections, I'll go change this. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org

Re: [DOCS] Missing doc for operator args in alter extension

what to do for unary operators (i.e. replace the type on the missing side with NONE). Patch to fix the doc attached. I think we might want to make the synopsis, as well as the description of left_arg and right_arg, match what's on the DROP OPERATOR page. Thoughts? -- Robert Haas EnterpriseDB

Re: [DOCS] [HACKERS] Uppercase SGML entity declarations

On Tue, Apr 5, 2011 at 2:18 PM, Peter Eisentraut pete...@gmx.net wrote: On mån, 2011-04-04 at 15:02 -0400, Robert Haas wrote: AFAICT, the biggest problem with our existing toolchain is that it's hard for some people to get it working.  In theory, we have documentation that explains

Re: [DOCS] [HACKERS] Uppercase SGML entity declarations

On Tue, Apr 5, 2011 at 4:59 PM, Peter Eisentraut pete...@gmx.net wrote: On tis, 2011-04-05 at 14:55 -0400, Robert Haas wrote: and I've also had failures, I believe, from not being connected to the Internet, which is surprising because it's not at all obvious that building the docs should

Re: [HACKERS] [DOCS] found a very confusing and maybe outdated sentence

man pages anymore then we not need the sentence that tells that the tutorial won't take care about man pages. Oh, I interpreted that sentence to be talking about the features *of psql*, not the man pages. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Re: [DOCS] [HACKERS] Uppercase SGML entity declarations

but I guess I'm not sure what it accomplishes. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] [HACKERS] Uppercase SGML entity declarations

just apply it and move on. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] [HACKERS] Uppercase SGML entity declarations

On Mon, Apr 4, 2011 at 2:42 PM, Tom Lane t...@sss.pgh.pa.us wrote: Robert Haas robertmh...@gmail.com writes: Even if that doesn't turn out to be the case, this is pretty harmless, so maybe we should just apply it and move on. I have no great objection to the patch as such; just wondering what

Re: [DOCS] [HACKERS] Uppercase SGML entity declarations

-toolsets.html However, in contrast to the vast majority of our documentation, it stinks. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http

Re: [DOCS] [HACKERS] Uppercase SGML entity declarations

of objections, I have pushed this patch.  Thanks. I think you still need to update Solution.pm to match. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http

Re: [DOCS] Migration page is out of date

a new version later, just wanted to put this note on the ML so that somebody would bug me before the end of 9.1 beta. Hey, you! -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make

Re: [DOCS] English Grammar question

different meanings. I actually find both phrasings a bit awkward, though. What we're really trying to do here is provide the links, but that is sometimes better done in a footnote or bibliography than in the middle of a body of text. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com

Re: [DOCS] found a very confusing and maybe outdated sentence

isn't correct installed just because docs aren't installed. Which also isn't really true. Honesty, I just would like to drop the whole sentences. What do you think? +1 for deleting the entire sentence. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Re: [DOCS] patch for createdb section in tutorial

- really characters? shouldn't it be bytes? I just tested - creating a database by using German umlauts let me get sure - it are bytes not characters. Here is the patch with the correction - I just changed the word characters into bytes. Committed and back-patched all the way. -- Robert Haas

Re: [DOCS] 9.1 release notes

On Thu, Mar 24, 2011 at 5:27 PM, Bruce Momjian br...@momjian.us wrote: Robert Haas wrote: On Sun, Mar 20, 2011 at 12:13 AM, Bruce Momjian br...@momjian.us wrote: I have completed and committed my draft of the 9.1 release notes. ?They will be continually updated and improved as we reach final

[DOCS] documenting contrib modules (was Re: Building PDFs error)

point, too, but maybe that should left for phase 2. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] explaining context column of pg_settings

On Thu, Mar 10, 2011 at 10:09 PM, Bruce Momjian br...@momjian.us wrote: What did we ever do with this idea? Nobody felt like putting in the amount of work required to hammer out the details, I think. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Re: [DOCS] explaining context column of pg_settings

On Fri, Mar 11, 2011 at 11:03 AM, Bruce Momjian br...@momjian.us wrote: I am unclear where to put this as well so I suggest we just put it in catalogs.sgml and be done with it. Please propose a specific patch so we can complain about it. :-) -- Robert Haas EnterpriseDB: http

Re: [DOCS] explaining context column of pg_settings

On Fri, Mar 11, 2011 at 12:37 PM, Tom Lane t...@sss.pgh.pa.us wrote: Bruce Momjian br...@momjian.us writes: Robert Haas wrote: Please propose a specific patch so we can complain about it.  :-) I am proposing Tom's:       http://archives.postgresql.org/pgsql-docs/2010-12/msg3.php That's

Re: [DOCS] Sync rep doc corrections

On Wed, Mar 9, 2011 at 11:43 PM, Bruce Momjian br...@momjian.us wrote: Thom Brown wrote: On 7 March 2011 22:31, Robert Haas robertmh...@gmail.com wrote: On Mon, Mar 7, 2011 at 6:16 AM, Thom Brown t...@linux.com wrote: On 7 March 2011 15:27, Thom Brown t...@linux.com wrote: I've attached

Re: [DOCS] Improve initdb and pg_controldata manual pages

. That's not the question. The question is whether the changes that you are proposing to make are in fact improvements. I believe that's something that reasonable people can disagree about. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via

  1   2   3   >