grants gives - Search results in mailing lists
Mailing lists >> pgsql-patches >> Thread
2008-09-02 14:23:25 | Re: WIP Join Removal (Tom Lane)
give up immediately if it's a join or not a table. */ if (checkrel->reloptkind == RELOPT_JOINREL || checkrel->rtekind != RTE_RELATION) return; Maybe you should also check for checkrel->indexlist == NIL here, since there
Mailing lists >> pgsql-patches >> Thread
2008-06-01 16:14:22 | Re: Feature: give pg_dump a WHERE clause expression (Davy Durham)
On Sun, 2008-06-01 at 10:43 -0400, Tom Lane wrote: Well, my primary
Mailing lists >> pgsql-patches >> Thread
2007-07-08 14:44:11 | Re: dblink connection security (Joe Conway)
gives us something handy to point to as a workaround when people complain we broke their apps. If there are no objections I'll commit this later today. Thanks, Joe Index: contrib/dblink/dblink.c =================================================================== RCS file: /cvsroot/pgsql/contrib/dblink/dblink.c
Mailing lists >> pgsql-patches >> Thread
2007-05-17 05:45:38 | Re: Updateable cursors patch (FAST PostgreSQL)
gives 'Where current of cursor' it essentially + * is 'where ctid = const'. So we create such a where clause and return + * it. This will then be transformed like any other where clause. In our + * case this
Mailing lists >> pgsql-patches >> Thread
2007-03-01 10:23:03 | Re: WIP Patch - Updateable Cursors (Simon Riggs)
grant a BSD licence on theirs." Deadlock. How do we know that you'll ever give
Mailing lists >> pgsql-patches >> Thread
2007-01-16 07:32:34 | pg_dumpall -f option (Dave Page)
gives us some abstraction and type checking. *************** *** 166,172 **** /* Create a new archive */ extern Archive *CreateArchive(const char *FileSpec, const ArchiveFormat fmt, ! const int compression); /* The --list option */ extern void PrintTOCSummary(Archive *AH, RestoreOptions *ropt
Mailing lists >> pgsql-patches >> Thread
2006-08-07 14:57:53 | IDENTITY/GENERATED columns (Zoltan Boszormenyi)
GRANT {INSERT|UPDATE|ALL} ON table automatically gives UPDATE permission for the supporting sequence (missing
Mailing lists >> pgsql-patches >> Thread
2006-07-11 16:59:01 | [patch 9/9] Include code for bignum math (Marko Kreen)
granted, free of charge, to any person + obtaining a copy of this software and associated documentation files + (the "Software"), to deal in the Software without restriction, + including without limitation the rights to use, copy, modify
Mailing lists >> pgsql-patches >> Thread
2006-04-22 08:50:49 | Re: [HACKERS] Automatically setting work_mem (Simon Riggs)
grant you, but the more memory you give a sort the smaller number of runs
Mailing lists >> pgsql-patches >> Thread >> Search in thread (3)
2006-01-06 18:32:45 | Re: [HACKERS] Inconsistent syntax in GRANT (Bruce Momjian)
GRANT UPDATE ON seq1 TO PUBLIC; do we give them nextval() and setval() permissions? If they
Mailing lists >> pgsql-patches >> Thread >> Search in thread (2)
2006-01-04 02:38:04 | Re: TRUNCATE, VACUUM, ANALYZE privileges (daveg)
grant "truncate". If giving truncate its very own permission is too wasteful of permission bits
Mailing lists >> pgsql-patches >> Thread
2005-11-18 16:01:31 | DROP OWNED again (Alvaro Herrera)
gives the objects away to some other role. It doesn't touch grants. So if a role
Mailing lists >> pgsql-patches >> Thread
2005-11-02 14:28:44 | Re: [HACKERS] Reducing the overhead of NUMERIC data (Simon Riggs)
give problems. The above on-disk format showed sign & weight together, whereas the current code has sign and dscale together. Trying to put sign and weight together is somewhat difficult, since weight is itself
Mailing lists >> pgsql-patches >> Thread
2005-08-11 01:23:32 | Re: [HACKERS] For review: Server instrumentation patch (Bruce Momjian)
giving length bytes.
+
+
+ pg_dir_ls lists all filenames in the named directory.
+
+
+
+ The functions shown in
Mailing lists >> pgsql-patches >> Thread
2005-07-07 13:43:38 | Re: Dependencies on shared objects (Alvaro Herrera)
give them to someone else (REASSIGN OWNED -- better wording?). An important distinction to be made is which dependencies are "auto" and which ones are "normal". It's clear that OWNER entries cannot be AUTO. OTOH