[DOCS] Incorrect REVOKE command in docs

2003-08-04 Thread Stephen Frost
Greetings, The 'REVOKE' command given in section 2.8.4 under Chapter 2. "Data Definition" is not correct. The command should be: REVOKE CREATE ON SCHEMA public FROM PUBLIC; Note that 'SCHEMA' is missing. This is at least on the web page: http://www.postgresql.org/docs/7.3/static/ddl-

Re: [DOCS] Proposed doc-patch: Identifying the Current WAL file

2006-04-17 Thread Stephen Frost
* Bruce Momjian ([email protected]) wrote: > In the first case, x2 is current, having be just switched to from x1, > while in the second case, x1 is current. In BSD, you can use ls -ltT to > see the seconds, but in Linux it is something different, and I am sure > there are some operating syst

Re: [DOCS] pg_file_settings and catalog.sgml

2015-06-12 Thread Stephen Frost
* Fujii Masao ([email protected]) wrote: > On Fri, Jun 12, 2015 at 1:47 AM, Fujii Masao wrote: > > Hi, > > > > System catalogs and views should be listed in alphabetical order, > > but only pg_file_settings view not. The attached patch fixes this > > alphabetization. > > > > The patch also fix

Re: [DOCS] sepgsql and row-level security

2015-10-16 Thread Stephen Frost
Heikki, * Heikki Linnakangas ([email protected]) wrote: > The docs on sepgsql says > (http://www.postgresql.org/docs/9.5/static/sepgsql.html#SEPGSQL-LIMITATIONS): > > >PostgreSQL does not support row-level access; therefore, sepgsql does > >not support it either. > > Should that be adjust

Re: [DOCS] sepgsql and row-level security

2015-11-13 Thread Stephen Frost
Heikki, * Heikki Linnakangas ([email protected]) wrote: > The docs on sepgsql says > (http://www.postgresql.org/docs/9.5/static/sepgsql.html#SEPGSQL-LIMITATIONS): > > >PostgreSQL does not support row-level access; therefore, sepgsql does > >not support it either. > > Should that be adjust

Re: [DOCS] A typo in install-windows.sgml

2016-07-08 Thread Stephen Frost
Alexander, * Alexander Law ([email protected]) wrote: > There is a typo in install-windows,sgml. Patch attached. Fix pushed. Thanks! Stephen signature.asc Description: Digital signature

Re: [DOCS] A hyphen missing in runtime.sgml

2016-07-13 Thread Stephen Frost
* Alexander Law ([email protected]) wrote: > I've found a hyphen missing in runtime.sgml. Patch attached. Fix pushed. Thanks! Stephen signature.asc Description: Digital signature

Re: [DOCS] Default privileges not working

2016-09-29 Thread Stephen Frost
Greetings, * [email protected] ([email protected]) wrote: > Thanks for the reply. [...] > alter default privileges in schema public grant select on tables to > "test_readonly", "test_readwrite", "test_power"; > alter default privileges in schema public grant insert, update, delete on > tables to "te

Re: [DOCS] Default privileges not working

2016-09-30 Thread Stephen Frost
Jozef, * Jozef Pažin ([email protected]) wrote: > -- grant for new tables > -- only users "postgres" and "test_power" can create tables; > alter default privileges for role "test_power" in schema public grant > select on tables to "test_readonly", "test_readwrite", "test_power"; > alter default pri

Re: [DOCS] Missing important information in backup.sgml

2016-11-16 Thread Stephen Frost
Gunnar, all, * Gunnar "Nick" Bluth ([email protected]) wrote: > Am 16.11.2016 um 11:37 schrieb Gunnar "Nick" Bluth: > > I ran into this issue (see patch) a few times over the past years, and > > tend to forget it again (sigh!). Today I had to clean up a few hundred > > GB of unarchived

Re: [DOCS] Missing important information in backup.sgml

2016-11-23 Thread Stephen Frost
Greetings, * Gunnar "Nick" Bluth ([email protected]) wrote: > Now, what could happen is All you need is for the archive server to be reset at the wrong time (and there are a lot of potential "wrong times" to choose from) and you'll end up with an incomplete archive. > a) complete DC power

Re: [DOCS] Missing important information in backup.sgml

2016-11-29 Thread Stephen Frost
Greetings, * Gunnar "Nick" Bluth ([email protected]) wrote: > Am 23.11.2016 um 21:41 schrieb Stephen Frost: > > * Gunnar "Nick" Bluth ([email protected]) wrote: > > One of the very important things that should be done as part of a backup >

Re: [DOCS] wrong column header text in grant doc page

2017-04-24 Thread Stephen Frost
Dmitriy, * Dmitriy Olshevskiy ([email protected]) wrote: > please, check the column header text " Column access privileges" > in the GRANT doc > page. I > think there must be "Column privileges", Ah, yes, though the actual \dp mytable ou

Re: [DOCS] Problems with ROW LEVEL SECURITY

2017-05-10 Thread Stephen Frost
Greetings, * [email protected] ([email protected]) wrote: > This works in version 9.3? No, RLS was not added to PostgreSQL until 9.5. Thanks! Stephen signature.asc Description: Digital signature

Re: [DOCS] Use of term Master/Slave

2017-08-01 Thread Stephen Frost
Alvaro, all, * Alvaro Herrera ([email protected]) wrote: > Simon Riggs wrote: > > On 31 July 2017 at 22:13, wrote: > > > The following documentation comment has been logged on the website: > > > > > > Page: https://www.postgresql.org/docs/9.6/static/release-9-6.html > > > Description: > >

Re: [DOCS] Row Level Security Policies documentation doesn't mention lack of support for views

2017-08-30 Thread Stephen Frost
David, Bruce, * David G. Johnston ([email protected]) wrote: > The CREATE VIEW documentation links to > > https://www.postgresql.org/docs/9.6/static/rules-privileges.html > > which covers this dynamic in considerable detail (and there is a blurb on > the CREATE VIEW page as well), and s

Re: [DOCS] inappropriate word 'victim'

2017-10-03 Thread Stephen Frost
Tom, all, * Tom Lane ([email protected]) wrote: > "Jonathan S. Katz" writes: > > So there is a precedent for using “target” for this command. > > I wouldn't object to substituting "target" for "victim"; they're both > pretty specific, and there's little risk of misunderstanding which > database

[DOCS] Migration to pglister - Before

2017-11-20 Thread Stephen Frost
Greetings, We will be migrating these lists to pglister in the next few minutes. This final email on the old list system is intended to let you know that future emails will have different headers and you will need to adjust your filters. The changes which we expect to be most significant to user