[COMMITTERS] npgsql - Npgsql2: Fixed line endings.

Log Message: --- Fixed line endings. Modified Files: -- Npgsql2/testsuite/noninteractive/NUnit20: TypesTests.cs (r1.12 -> r1.13) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/testsuite/noninteractive/NUnit20/TypesTests.cs?r1=1.12&r2=1.13) --

[COMMITTERS] pgsql: Don't forget to de-escape the password field in .pgpass.

Don't forget to de-escape the password field in .pgpass. This has been broken just about forever (or more specifically, commit 7f4981f4af1700456f98ac3f2b2d84959919ec81) and nobody noticed until Richard Huxton reported it recently. Analysis and fix by Ross Reedstrom, although I didn't use his patc

[COMMITTERS] pgsql: Add ALTER DOMAIN ... RENAME

Add ALTER DOMAIN ... RENAME You could already rename domains using ALTER TYPE, but with this new command it is more consistent with how other commands treat domains as a subcategory of types. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f90dd28062db2128a340fbe02f5

[COMMITTERS] pgsql: Add a security_barrier option for views.

Add a security_barrier option for views. When a view is marked as a security barrier, it will not be pulled up into the containing query, and no quals will be pushed down into it, so that no function or operator chosen by the user can be applied to rows not exposed by the view. Views not configur

Re: [COMMITTERS] pgsql: Add a security_barrier option for views.

Robert Haas writes: > Add a security_barrier option for views. Where's the catversion bump for having broken stored rules/views? regards, tom lane -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://ww

Re: [COMMITTERS] pgsql: Add a security_barrier option for views.

Excerpts from Tom Lane's message of jue dic 22 18:39:18 -0300 2011: > Robert Haas writes: > > Add a security_barrier option for views. > > Where's the catversion bump for having broken stored rules/views? I'm starting to wonder if we should have a git hook of some sort to check for this ... --

Re: [COMMITTERS] pgsql: Add a security_barrier option for views.

On Thu, Dec 22, 2011 at 4:17 PM, Robert Haas wrote: > Add a security_barrier option for views. > you have some docs typos here, for the rest: cool. doc/src/sgml/ref/create_view.sgml """ + This clause specifies optional parameters for a view; currently, the + only suppored parameter nam

Re: [COMMITTERS] pgsql: Add a security_barrier option for views.

Alvaro Herrera writes: > Excerpts from Tom Lane's message of jue dic 22 18:39:18 -0300 2011: >> Robert Haas writes: >>> Add a security_barrier option for views. >> Where's the catversion bump for having broken stored rules/views? > I'm starting to wonder if we should have a git hook of some sor

[COMMITTERS] pgsql: Catversion bump for commit 0e4611c0234d89e288a53351f775c59522bae

Catversion bump for commit 0e4611c0234d89e288a53351f775c59522baed7c. It changed the format of stored rules. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/99b60fc04e53c09ca630d2798acb3768a778dc47 Modified Files -- src/include/catalog/catversion.h |2

Re: [COMMITTERS] pgsql: Add a security_barrier option for views.

Excerpts from Tom Lane's message of jue dic 22 19:09:54 -0300 2011: > > Alvaro Herrera writes: > > Excerpts from Tom Lane's message of jue dic 22 18:39:18 -0300 2011: > >> Robert Haas writes: > >>> Add a security_barrier option for views. > > >> Where's the catversion bump for having broken st

[COMMITTERS] pgsql: Typo fixes.

Typo fixes. All noted by Jaime Casanova. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/0510b62d91151b9d8c1fe1aa15c9cf3ffe9bf25b Modified Files -- doc/src/sgml/ref/create_view.sgml |2 +- doc/src/sgml/rules.sgml |4 ++-- 2 files changed,