Re: Users/Roles do not align.
There's a few things wrong about this part anyway- namely that we've got FDWs now, and there's certainly other cluster-wide things that exist beyond the specific items listed, so I wonder if perhaps we should just stop trying to list everything here. Inspiring answer! After some inquiry I became aware, that we do not have only 2 levels of 'belong-to' but 3: tables, views, operators, and much more objects belong to a schema; schemata, extensions (e.g. FDW), and more(?) belong to a database; databases, roles, tablespaces, and more belong to a cluster. Two aspects of 'belong-to' are: object names are unique within their level, and objects are automatically known everywhere within their level. Information about such dependencies and their consequences is spread across different chapters of the documentation and the System Catalog. Of course the chapter about roles/users is not suitable to explain the details. But it's important to know the hierarchy, it shut be summarized somewhere. Kind regards, J. Purtz
Examples required in || 5.10. Table Partitioning
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/ddl-partitioning.html Description: Hello , As I'm searching for the official documentation of Hash Partition and List Partition with example with more description the only information is found is as below : List Partitioning The table is partitioned by explicitly listing which key values appear in each partition. Hash Partitioning The table is partitioned by specifying a modulus and a remainder for each partition. Each partition will hold the rows for which the hash value of the partition key divided by the specified modulus will produce the specified remainder. But how to create and manage these above 2 partition is not explained in documentation properly officially.for further information related to these 2 partition we need to search private blogs,because of lack of information provided in the documentation 5.10. Table Partitioning I only saw the Range partition example throughout the Table Partitioning . I request you to modify the 5.10. Table Partitioning section and make it more informative as Table Partition is very important in PostgreSQL . Kind Regards, Tanay Purnaye.
Re: Documentation: 21.5. Default Roles
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, should be safe (as long >>> as we add an entry to that table in pgweb). >>> >>> As for back branches, I think we have to say that it's too close to >>> the minor release to safely have something done in pgweb before then. >> >> This part I agree on, but let's sync offline to see if there is >> something within reason, with a preference to *not* rush if we're >> worried about breaking something right before release. > > Folks, is it Thursday. Can we revert this and return to it when we are > not rushed? Alternatively, can someone who controls all the moving > parts, like redirects and Stephen's patch additions take ownership of > this issue, with authority to revert the patch if things are too close? Magnus and I briefly discussed what it would take, but the probability of having the redirects ready on pgweb before the release is slim-to-none, as we'd like to thoroughly test. We can start experimenting with it now, and commit a fix after the release. I don't have the power to revert changes directly to the documentation in core, so I cannot take ownership of that part. However, I am happy to own the completion of the redirect feature. Thanks, Jonathan signature.asc Description: OpenPGP digital signature
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, should be safe (as long > >>> as we add an entry to that table in pgweb). > >>> > >>> As for back branches, I think we have to say that it's too close to > >>> the minor release to safely have something done in pgweb before then. > >> > >> This part I agree on, but let's sync offline to see if there is > >> something within reason, with a preference to *not* rush if we're > >> worried about breaking something right before release. > > > > Folks, is it Thursday. Can we revert this and return to it when we are > > not rushed? Alternatively, can someone who controls all the moving > > parts, like redirects and Stephen's patch additions take ownership of > > this issue, with authority to revert the patch if things are too close? > > Magnus and I briefly discussed what it would take, but the probability > of having the redirects ready on pgweb before the release is > slim-to-none, as we'd like to thoroughly test. > > We can start experimenting with it now, and commit a fix after the release. > > I don't have the power to revert changes directly to the documentation > in core, so I cannot take ownership of that part. However, I am happy to > own the completion of the redirect feature. I can own the core bits, since you've offered to take on the web pieces. :) Given the discussion, barring objections, I'll revert the changes tomorrow and then work with Jonathan and Magnus to try and get the website redirect stuff working so that we can make this change in a future release. Thanks, Stephen signature.asc Description: PGP signature
Re: Documentation: 21.5. Default Roles
On Thu, Feb 6, 2020 at 11:05:04AM -0500, Stephen Frost wrote: > * Jonathan S. Katz (jk...@postgresql.org) wrote: > > I don't have the power to revert changes directly to the documentation > > in core, so I cannot take ownership of that part. However, I am happy to > > own the completion of the redirect feature. > > I can own the core bits, since you've offered to take on the web pieces. > :) > > Given the discussion, barring objections, I'll revert the changes > tomorrow and then work with Jonathan and Magnus to try and get the > website redirect stuff working so that we can make this change in a > future release. OK, thanks everyone. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
