grants gives - Search results in mailing lists
Mailing lists >> pgsql-committers >> Thread
2024-10-11 19:02:54 | pgsql: Add pg_ls_summariesdir(). (Nathan Bossart)
granting privileges on pg_ls_dir(), which allows listing the contents of many other directories. This commit also gives
Mailing lists >> pgsql-committers >> Thread
2024-04-01 20:46:40 | [MASSMAIL] pgsql: Rearrange pg_dump's handling of large objects for better efficie (Tom Lane)
grants); the archive format wouldn't require that, but pg_dump's representation of DumpableObjects does. It seems unlikely that either restriction will be problematic for databases with huge numbers of blobs. The metadata
Mailing lists >> pgsql-committers >> Thread
2022-08-22 15:42:29 | pgsql: Make role grant system more consistent with other privileges. (Robert Haas)
give WITH GRANT OPTION on a privilege back to a role which granted it directly
Mailing lists >> pgsql-committers >> Thread
2021-04-05 17:45:12 | pgsql: Add pg_read_all_data and pg_write_all_data roles (Stephen Frost)
GRANT that user access to all tables, schemas, et al, without that role being a superuser. This address that by adding a "pg_read_all_data" role which implicitly gives
Mailing lists >> pgsql-committers >> Thread
2017-11-09 20:56:15 | [COMMITTERS] pgsql: Restrict lo_import()/lo_export() via SQL permissions nothard-wi (Tom Lane)
give permissions on these functions to anyone but a superuser, we've been moving away from hard-wired permission checks inside functions in favor of using the SQL permission system to control access. Bring
Mailing lists >> pgsql-committers >> Thread
2016-02-08 21:42:11 | Michael Paquier (Andrew Dunstan)
granted to committers who are also on the -security list. However, Michael is not a committer, and has requested access. I've actually thought for some time that there is plenty of reason to give
Mailing lists >> pgsql-committers >> Thread
2008-12-19 12:25:26 | pgsql: SQL/MED catalog manipulation facilities This doesn't do any (petere@postgresql.org (Peter Eisentraut))
gives modules like plproxy and dblink a standardized and future-proof system for managing their connection information. Martin Pihlak and Peter Eisentraut Modified Files: -------------- pgsql/doc/src/sgml: catalogs.sgml (r2.184 -> r2.185) (http:///cvsweb.cgi/pgsql/doc/src/sgml/catalogs.sgml?r1=2.184&r2=2.185) features.sgml (r2.29 -> r2.30
Mailing lists >> pgsql-committers >> Thread
2005-11-21 08:49:37 | pgsql: Implement DROP OWNED and REASSIGN OWNED. (alvherre@svr1.postgresql.org (Alvaro Herrera))
granted to them, or giving the owned objects to someone else, through the use of the data
Mailing lists >> pgsql-committers >> Thread
2002-09-19 23:42:40 | pgsql-server/contrib/fulltextindex fti.sql.in (momjian@postgresql.org (Bruce Momjian - CVS))
grants execute privileges to public for the fti() function. Should we go through and give