Re: Row Level Security Execution within the SQL Evaluation Pipeline

Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > RLS documentation seems to say the user's predicate is evaluated AFTER the > policy is evaluated. This presents to me an issue that I can't wrap my head > around, and seems to confuse others as well. > > Setup: > 1. We have a pol

Re: Make SSPI documentation clearer

Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > Page: https://www.postgresql.org/docs/15/sspi-auth.html > Description: > > The [current SSPI > documentation](https://www.postgresql.org/docs/current/sspi-auth.html) > reads: > > "SSPI authentication only works when both server

Re: Make SSPI documentation clearer

On 13.03.23 10:00, Tomas Pospisek wrote: > > On 13.03.23 01:36, Stephen Frost wrote: > > > > > * PG Doc comments form (nore...@postgresql.org) wrote: > > > > Page: https://www.postgresql.org/docs/15/sspi-auth.html > > > > Description: > > > > &

Re: pg_basebackup application does not dump all database objects

Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > It would be good to point out on the pg_basebackup documentation that it > behaves differently from > > SELECT * FROM pg_start_backup('label', true, false); > cp -a xxx yyy > SELECT * FROM pg_stop_backup(false, true); ... that's

Re: pg_basebackup application does not dump all database objects

Greetings, Please don't top-post on these lists. * Kristjan Mustkivi (sonicmon...@gmail.com) wrote: > Thank you very much for the feedback and a reference! I was under the > impression that pg_basebackup does everything > pg_start_backup/pg_stop_backup but with a more user-friendly manner > and a

Re: User mapping security

Greetings, * Bruce Momjian (br...@momjian.us) wrote: > On Tue, Jul 16, 2019 at 02:01:00AM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/10/postgres-fdw.html > > Description: > > > > Regardi

Re: unclear wording re: spoofing prevention on network connections

Greetings, On Sat, Dec 9, 2023 at 17:29 Bruce Momjian wrote: > On Fri, Dec 8, 2023 at 05:42:27PM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/16/preventing-server-spoofing.html > > Descri

Re: unclear wording re: spoofing prevention on network connections

Greetings, On Sat, Dec 9, 2023 at 18:02 David G. Johnston wrote: > On Saturday, December 9, 2023, Stephen Frost wrote: > >> >> >> The idea is that you can use both TLS and GSSAPI-with-encryption at the >> same time within a given cluster for connections but you wo

Re: Add a different archive_command example for Linux / Unix

Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > Hello, > in > https://www.postgresql.org/docs/16/continuous-archiving.html#BACKUP-ARCHIVING-WAL > the example given could be improved for Linux / Unix environment. > > As cp command is buffered it means it could return success al

Re: Add a different archive_command example for Linux / Unix

Greetings, * gp...@free.fr (gp...@free.fr) wrote: > Thanks Stephen for your detailed reply and broad perspective. > But I see the cp example command used **as is** most of the time. In those cases- how would changing it to be a dd command be helpful? The directory still wouldn't be fsync'd and th

Migration to PGLister - After

Greetings! This list has now been migrated to new mailing list software known as 'PGLister'. This migration will impact all users of this mailing list in one way or another. If you would like to unsubscribe from this mailing list, please click on 'Show Original' or 'Show Headers' in your client

Change to docs reporting form

Greetings, In order to avoid having emails generated from the doc reporting form be considered as spam by lots of people because it's clearly forged email, we've changed the 'From' to be a 'noreply' address and set the 'Reply-To' to be the original sender and the mailing list. Hopefully this chan

Re: Missing column_constraint explanation

Michael, * Michael Paquier (michael.paqu...@gmail.com) wrote: > On Wed, Dec 20, 2017 at 6:08 PM, PG Doc comments form > wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/9.6/static/sql-altertable.html > > Description: > >

Re: Is this still accurate?

Greetings, * Moser, Glen G (glen.mo...@charter.com) wrote: > Can someone confirm the accuracy of the information found at > https://www.postgresql.org/about/? > > Specifically the maximum data values in the screen shot below...it seems as > though this documentation might be out of date. The p

Re: Is this still accurate?

Greetings, * Moser, Glen G (glen.mo...@charter.com) wrote: > That's really the gist of the concern from a team member of mine. Not that > the 4TB number is wrong but that it could be misleading to assume that 4TB is > some sort of upper bound. > > That's how this concern was relayed to me and

Re: Missing column_constraint explanation

Michael, * Michael Paquier (michael.paqu...@gmail.com) wrote: > On Thu, Dec 21, 2017 at 12:15 PM, Stephen Frost wrote: > > Now, if we could do that in such a way that we avoid having to actually > > duplicate the 'source' for these productions into different places in &g

Re: Missing column_constraint explanation

Michael, * Michael Paquier (michael.paqu...@gmail.com) wrote: > On Sat, Jan 13, 2018 at 09:06:22PM -0500, Stephen Frost wrote: > > I'm not really sure that we want to go there for this case though. > > Perhaps others disagree, but that seems like a lot to avoid this > &

Re: Document the limit on the number of parameters

Greetings, * Bruce Momjian (br...@momjian.us) wrote: > On Tue, Jul 17, 2018 at 01:25:08PM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/10/static/sql-prepare.html > > Description: > > > > T

Re: Document the limit on the number of parameters

Greetings Tom, * Tom Lane (t...@sss.pgh.pa.us) wrote: > Stephen Frost writes: > > * Bruce Momjian (br...@momjian.us) wrote: > >> On Tue, Jul 17, 2018 at 01:25:08PM +, PG Doc comments form wrote: > >>> The backend protocol limits the number of parameters that ca

Re: Return codes for archive and restore commands

Greetings, * Michael Paquier (mich...@paquier.xyz) wrote: > On Wed, Nov 28, 2018 at 11:00:31AM +, PG Doc comments form wrote: > > For the archive command: > > <=128 There are not errors in the PostgreSQL log (messages with severity > > equal or higher than ERROR). Firstly 3 messages of type LO

Re: Return codes for archive and restore commands

Greetings, * Michael Paquier (mich...@paquier.xyz) wrote: > On Wed, Nov 28, 2018 at 09:39:58PM -0500, Stephen Frost wrote: > > Having discussed this quite a bit lately with David Steele and Magnus, > > it's pretty clear that we need to completely rip out how this works >

Re: Return codes for archive and restore commands

Greetings, * Michael Paquier (mich...@paquier.xyz) wrote: > On Wed, Nov 28, 2018 at 10:27:31PM -0500, Stephen Frost wrote: > > Yes, it couldn't be exactly the same as a generic background worker, > > that's a good point. We definitely need to make sure that the >

Re: Minor typo in sentence

Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/planner-stats.html > Description: > > There is typo in "14.2.2. Extended Statistics": > > > Statistics objects ar

Re: Minor typo in sentence

Greetings, * Stephen Frost (sfr...@snowman.net) wrote: > * PG Doc comments form (nore...@postgresql.org) wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/11/planner-stats.html > > Description

Re: SET ROLE documentation not entirely correct

Greetings, * Tom Lane (t...@sss.pgh.pa.us) wrote: > Joe Conway writes: > > On 4/25/19 1:08 PM, Joe Conway wrote: > >> There is one image which can be used as an example though: > >> https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=doc/src/sgml/storage.sgml;hb=HEAD > > > Here is a mor

Re: Google Season of Docs 2019 - PostgreSQL

Greetings, * Raghav Jajodia (jajodia.rag...@gmail.com) wrote: > I am Raghav Jajodia, a software engineer from Bangalore, India. I have been > a diligent open source contributor and have been a student under the > following: > 1. Google Summer of Code 2017 student > 2. OWASP Code Sprint Winner > 3.

Re: readability changes to postgres.sgml

Greetings, * Joshua D. Drake (j...@commandprompt.com) wrote: > attached While I'm all for working on improving the documentation and, in particular, our tutorials, the above description of what the suggested change is seems to be rather.. lacking, and the changes themselves don't come across as

Re: I'm surprised to see the word master here

Greetings, * Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote: > On 2019-09-25 00:28, Dave Cramer wrote: > > Ya, I was under that impression as well.  > > > > Dave Cramer > > > > > > On Tue, 24 Sep 2019 at 18:18, Renee > > wrote: > > > > I was und

Re: I'm surprised to see the word master here

Greetings, * Magnus Hagander (mag...@hagander.net) wrote: > On Wed, Oct 2, 2019 at 3:10 PM Jonathan S. Katz > wrote: > > On 10/2/19 7:39 AM, Chris Travers wrote: > > > On Wed, Oct 2, 2019 at 12:57 PM Erikjan Rijkers > > > wrote: > > > > > > On 2019-10-02 12:46, Peter E

Re: I'm surprised to see the word master here

Greetings, * Bruce Momjian (br...@momjian.us) wrote: > On Wed, Oct 2, 2019 at 03:04:55PM -0400, Stephen Frost wrote: > > I don't agree with this claim. While we could argue about if a hot > > standby is considered "active" or not, the vast majority of the world &g

Re: I'm surprised to see the word master here

Greetings, * Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote: > On 2019-10-08 18:39, Stephen Frost wrote: > > I'm also at a loss as to why we're discussing what to call 'master/ > > master' here since we don't actually use the term 'master/ma

Re: Documentation: 21.5. Default Roles

Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > The title is wrong. The roles are not defaults; they are predefined and > privileged. The title suggests that a user should expect to be assigned > these roles. "21.5 Sub-Administrator Roles" would be accurate--improving >

Re: Postgres.js driver - for Node.js

Greetings, * Jonathan S. Katz (jk...@postgresql.org) wrote: > On 1/8/20 7:59 PM, Tom Lane wrote: > > "Jonathan S. Katz" writes: > >> On 1/8/20 7:00 PM, Jonathan Buhacoff wrote: > >>> I'm wondering if the short list in the documentation [2] could be > >>> replaced with a link to the corresponding

Re: Documentation: 21.5. Default Roles

Greetings, * Bruce Momjian (br...@momjian.us) wrote: > On Tue, Jan 7, 2020 at 11:46:31AM +0100, Laurenz Albe wrote: > > On Fri, 2019-12-27 at 12:16 -0500, Bruce Momjian wrote: > > > On Fri, Dec 27, 2019 at 05:44:10AM +, PG Doc comments form wrote: > > > > The following documentation comment h

Re: Documentation: 21.5. Default Roles

Greetings, * Alvaro Herrera (alvhe...@2ndquadrant.com) wrote: > 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 pur

Re: Users/Roles do not align.

Greetings, * Jürgen Purtz (juer...@purtz.de) wrote: > >Based on this, I believe Section 5.9 should read: > >`A PostgreSQL database cluster contains one or more named databases. Roles > >are shared across the entire cluster, but no other data is shared across > >databases. Any given client connecti

Re: Documentation: 21.5. Default Roles

Greetings, * Jonathan S. Katz (jk...@postgresql.org) wrote: > On 2/6/20 12:11 AM, Bruce Momjian wrote: > > On Tue, Feb 4, 2020 at 11:31:19AM -0500, Jonathan Katz wrote: > >>> Using this feature to handle the rename of a file *between* major > >>> versions, thus leaving the changes in master, shou

Re: Documentation: 21.5. Default Roles

Greetings, On Sun, Feb 9, 2020 at 14:24 Tom Lane wrote: > Stephen Frost writes: > > * Jonathan S. Katz (jk...@postgresql.org) wrote: > >> On 2/6/20 12:11 AM, Bruce Momjian wrote: > >>> Folks, is it Thursday. Can we revert this and return to it when we are > &g

Re: Logical replication subscription owner

Greetings, * Alvaro Herrera (alvhe...@2ndquadrant.com) wrote: > On 2020-Apr-15, PG Doc comments form wrote: > > If the logical replication subscription is owned by a role that is not > > allowed to login (for example, if the LOGIN privilege is removed after the > > subscription is created) then th

Re: Logical replication subscription owner

Greetings, * Tom Lane (t...@sss.pgh.pa.us) wrote: > Alvaro Herrera writes: > > I had it in my mind that LOGIN was for regular (SQL-based) login, and > > REPLICATION was for replication login, and that they were orthogonal. > > Yeah, that's what I would've expected. Otherwise, is REPLICATION > w

Re: Documentation: 21.5. Default Roles

Greetings, * Magnus Hagander (mag...@hagander.net) wrote: > On Sat, Apr 25, 2020 at 1:38 AM Jonathan S. Katz > wrote: > > > On 4/9/20 11:45 PM, Bruce Momjian wrote: > > > On Thu, Apr 9, 2020 at 08:47:56PM -0400, Jonathan Katz wrote: > > >> On 4/9/20 4:57 PM, Bruce Momjian wrote: > > >>> Jonatha

Re: Logical replication subscription owner

Greetings, * Tom Lane (t...@sss.pgh.pa.us) wrote: > Michael Paquier writes: > > Not to make the life of everybody more complicated here, but I don't > > agree. LOGIN and REPLICATION are in my opinion completely orthogonal > > and it sounds more natural IMO that a REPLICATION user should be able

Re: Client parameter list omits timezone

Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > Page: https://www.postgresql.org/docs/11/libpq-connect.html > Description: > > I am looking for a complete list of parameters that I can pass in the > "connect"/"open database connection" list on the client (in this case, > githu

Re: Client parameter list omits timezone

Greetings, Please don't top-post on these lists. * Kevin Burke (ke...@meter.com) wrote: > I guess my broader issue is that it's hard to figure out how to configure > things like the timezone in a given client. Generally, you pass some things > as parameters in the connection string but it's not o

Re: "stable storage"

Greetings, * Peter Geoghegan (p...@bowt.ie) wrote: > On Fri, Aug 21, 2020 at 3:12 PM Bruce Momjian wrote: > > > Is "stable storage" the same as "durable storage"? Should we rename > > > "stable storage" mentions to "durable storage"? > > > > I have developed the attached doc patch to change "sta

Re: Openssl v3_ca

Greetings, * Bruce Momjian (br...@momjian.us) wrote: > A few years ago I figured out how to create intermediate certificates > that are transferred across OpenSSL connections by using the v3_ca > extension, and added this to the PG documentation. > > I have now just figured out that v3_ca is just

Re: Possible mistake in backup documentation

Greetings, * Laurenz Albe (laurenz.a...@cybertec.at) wrote: > On Fri, 2020-09-25 at 14:50 +0200, Magnus Hagander wrote: > > On Fri, Sep 25, 2020 at 2:32 PM Laurenz Albe > > wrote: > > > On Tue, 2020-09-22 at 14:17 +, PG Doc comments form wrote: > > > > In "25.3.3.2. Making An Exclusive Low-L

Re: Documentation: 21.5. Default Roles

Greetings, * Bruce Momjian (br...@momjian.us) wrote: > OK, Stephen, I believe you have a more comprehensive patch to make this > change. When can you complete it? The above email is from April. Having gone back through this thread (again) to figure out where we are on this, and chatting with Jo

Re: Documentation: 21.5. Default Roles

Greetings, * Bruce Momjian (br...@momjian.us) wrote: > On Fri, Oct 23, 2020 at 05:40:37PM -0400, Stephen Frost wrote: > > Therefore, on the whole, the proposal that I would put out there is: > > > > - Rename everything (code, docs, etc) to 'predefined roles&

Re: Trusted versus untrusted Pl language

Greetings, * Steven Pousty (steve.pou...@gmail.com) wrote: > If you consider the application developer or data scientist's perspective > it makes total sense. I don't like the pattern of appdevs always working as > the postgres user, it encourages bad patterns and can often blow up when > you move

Re: incoorect restore_command

Greetings, * Philipp Gramzow (p...@philphonic.de) wrote: > Am 24.02.2021 um 06:49 schrieb Michael Paquier: > >On Mon, Feb 22, 2021 at 07:36:28AM +, PG Doc comments form wrote: > >>I've been trying out saving and restoring compressed archive logs. The > >>restore_command stated in the docs at "

Re: TLS acronym

ry for TLS. Updated patch attached, mainly just adding author/reviewed-by/discussion items. Barring objections, I'll plan to commit and back-patch this all the way over the weekend sometime. Thanks! Stephen From 07c3564caa5dab0c198d261b7d5e17f1082dc871 Mon Sep 17 00:00:00 2001 From: Stephen

Re: TLS acronym

Greetings, * Stephen Frost (sfr...@snowman.net) wrote: > * Daniel Gustafsson (dan...@yesql.se) wrote: > > As discussed in the NSS thread, we've had TLS defined as an since > > commit c6763156589 in 2014 without actually having it defined in > > acronyms.sgml. >

Re: Documentation: 21.5. Default Roles

Greetings, * Stephen Frost (sfr...@snowman.net) wrote: > * Bruce Momjian (br...@momjian.us) wrote: > > On Fri, Oct 23, 2020 at 05:40:37PM -0400, Stephen Frost wrote: > > > Therefore, on the whole, the proposal that I would put out there is: > > > > > > - Re

Re: Documentation: 21.5. Default Roles

Greetings, * Jonathan S. Katz (jk...@postgresql.org) wrote: > On 4/1/21 3:34 PM, Stephen Frost wrote: > > * Stephen Frost (sfr...@snowman.net) wrote: > > >> I've written a patch to begin to make this change and sent it into > >> -hackers for comments, thread i

Re: Improve documentation for pg_upgrade, standbys and rsync

Greetings, * Laurenz Albe (laurenz.a...@cybertec.at) wrote: > I revently tried to upgrade a standby following the documentation, > but I found it hard to understand, and it took me several tries to > get it right. This is of course owing to my lack of expertise with > rsync, but I think the docum

Re: Link missing in the 14 release notes

Greetings, * Euler Taveira (eu...@eulerto.com) wrote: > On Wed, Jun 30, 2021, at 11:47 AM, Daniel Westermann (DWE) wrote: > > "Add predefined roles pg_read_all_data and pg_write_all_data (Stephen Frost) > > > > These non-login roles can be used to give read or write per

Re: Link missing in the 14 release notes

Greetings, On Thu, Jul 1, 2021 at 21:35 Bruce Momjian wrote: > On Thu, Jul 1, 2021 at 05:46:16PM -0400, Stephen Frost wrote: > > Greetings, > > > > * Euler Taveira (eu...@eulerto.com) wrote: > > > On Wed, Jun 30, 2021, at 11:47 AM, Daniel Westermann (DWE) wrote:

Re: Link missing in the 14 release notes

Greetings, On Thu, Jul 1, 2021 at 21:57 Bruce Momjian wrote: > On Thu, Jul 1, 2021 at 09:47:47PM -0400, Stephen Frost wrote: > > On Thu, Jul 1, 2021 at 21:35 Bruce Momjian wrote: > > I normally link to only the _first_ mention of something, and since > they > >

Re: Link missing in the 14 release notes

Greetings, * Bruce Momjian (br...@momjian.us) wrote: > On Fri, Jul 2, 2021 at 05:15:23AM +, Daniel Westermann (DWE) wrote: > > >On Thu, Jul  1, 2021 at 10:01:46PM -0400, Stephen Frost wrote: > > >Only the first mention of "factorial()" uses a link;  the second

Re: Improve documentation for pg_upgrade, standbys and rsync

Greetings, * Laurenz Albe (laurenz.a...@cybertec.at) wrote: > On Wed, 2021-05-19 at 10:31 -0400, Stephen Frost wrote: > > * Laurenz Albe (laurenz.a...@cybertec.at) wrote: > > > I revently tried to upgrade a standby following the documentation, > > > but I found it hard

Re: Improve documentation for pg_upgrade, standbys and rsync

Greetings, * Laurenz Albe (laurenz.a...@cybertec.at) wrote: > Thanks for looking at this! Sure. Thanks for working on it! > On Fri, 2021-07-16 at 09:17 -0400, Stephen Frost wrote: > > > > An additional thing that we should really be mentioning is to tell > > > >

Re: psql's commit df9f599b is not documented

Greetings, * Tom Lane (t...@sss.pgh.pa.us) wrote: > Dave Cramer writes: > > I would agree. If it's worth coding it's worth documenting. Unless of > > course the intention is that this is temporary. > > Documenting it would mean committing to keeping it indefinitely, > which I think was exactly w

Re: Improve documentation for pg_upgrade, standbys and rsync

Greetings, * Robert Haas (robertmh...@gmail.com) wrote: > On Mon, Jul 26, 2021 at 3:11 PM Stephen Frost wrote: > > * Laurenz Albe (laurenz.a...@cybertec.at) wrote: > > > Thanks for looking at this! > > > > Sure. Thanks for working on it! > > Stephen, do y