On Thu, Jul 11, 2013 at 06:38:58PM -0400, Alvaro Herrera wrote:
> > I do find the "patch applied" emails helpful when I am reading email
> > threads, and I can see the patch was applied. For me, it closes the
> > loop, and sometimes the commit message isn't clear about what patch
> > thread it clo
Fixed incorrect description of EXEC SQL VAR command.
Thanks to MauMau for finding and fixing this.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/703bc145f773835637a8a01f2fe4cfb864835bb1
Modified Files
--
doc/src/sgml/ecpg.sgml | 12 +++---
Fixed incorrect description of EXEC SQL VAR command.
Thanks to MauMau for finding and fixing this.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/129e9dd1a2527a5a69d9761f11991a1857bcd91d
Modified Files
--
doc/src/sgml/ecpg.sgml | 12 +++---
Make comments reflect that omission of SPI_gettypmod() is intentional.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/448fee2e238ae4797e68d7d15b49f2fc52691547
Modified Files
--
src/backend/executor/spi.c |6 ++
src/pl/plpgsql/src/pl_exec.c |
Switch user ID to the object owner when populating a materialized view.
This makes superuser-issued REFRESH MATERIALIZED VIEW safe regardless of
the object's provenance. REINDEX is an earlier example of this pattern.
As a downside, functions called from materialized views must tolerate
running in
Switch user ID to the object owner when populating a materialized view.
This makes superuser-issued REFRESH MATERIALIZED VIEW safe regardless of
the object's provenance. REINDEX is an earlier example of this pattern.
As a downside, functions called from materialized views must tolerate
running in
Add session_preload_libraries configuration parameter
This is like shared_preload_libraries except that it takes effect at
backend start and can be changed without a full postmaster restart. It
is like local_preload_libraries except that it is still only settable by
a superuser. This can be a be
