Magnus Hagander writes:
> Support configurable eventlog application names on Windows
Some of the buildfarm members still don't like this patch ...
regards, tom lane
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subsc
On 25.10.2011 21:05, Magnus Hagander wrote:
Support configurable eventlog application names on Windows
This allows different instances to use the eventlog with different
identifiers, by setting the event_source GUC, similar to how
syslog_ident works.
Original patch by MauMau, heavily modified b
On Wed, Oct 26, 2011 at 16:41, Heikki Linnakangas
wrote:
> On 25.10.2011 21:05, Magnus Hagander wrote:
>>
>> Support configurable eventlog application names on Windows
>>
>> This allows different instances to use the eventlog with different
>> identifiers, by setting the event_source GUC, similar
Change FK trigger creation order to better support self-referential FKs.
When a foreign-key constraint references another column of the same table,
row updates will queue both the PK's ON UPDATE action and the FK's CHECK
action in the same event. The ON UPDATE action must execute first, else
the
Change FK trigger creation order to better support self-referential FKs.
When a foreign-key constraint references another column of the same table,
row updates will queue both the PK's ON UPDATE action and the FK's CHECK
action in the same event. The ON UPDATE action must execute first, else
the
Change FK trigger creation order to better support self-referential FKs.
When a foreign-key constraint references another column of the same table,
row updates will queue both the PK's ON UPDATE action and the FK's CHECK
action in the same event. The ON UPDATE action must execute first, else
the
Change FK trigger creation order to better support self-referential FKs.
When a foreign-key constraint references another column of the same table,
row updates will queue both the PK's ON UPDATE action and the FK's CHECK
action in the same event. The ON UPDATE action must execute first, else
the
Change FK trigger creation order to better support self-referential FKs.
When a foreign-key constraint references another column of the same table,
row updates will queue both the PK's ON UPDATE action and the FK's CHECK
action in the same event. The ON UPDATE action must execute first, else
the
Change FK trigger creation order to better support self-referential FKs.
When a foreign-key constraint references another column of the same table,
row updates will queue both the PK's ON UPDATE action and the FK's CHECK
action in the same event. The ON UPDATE action must execute first, else
the
Change FK trigger naming convention to fix self-referential FKs.
Use names like "RI_ConstraintTrigger_a_" for FK action triggers and
"RI_ConstraintTrigger_c_" for FK check triggers. This ensures the
action trigger fires first in self-referential cases where the very same
row update fires
MingW doesn't support wcstombs_s()...
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/2b64f3f17a4c1064008ea7cfe52d8eabe0b86370
Modified Files
--
src/bin/pgevent/pgevent.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
--
Sent via pgsql-com
Implement streaming xlog for backup tools
Add option for parallel streaming of the transaction log while a
base backup is running, to get the logfiles before the server has
removed them.
Also add a tool called pg_receivexlog, which streams the transaction
log into files, creating a log archive wi
Fix pg_bsd_indent bug where newlines were not being trimmed from typedef
lines. Update pg_bsd_indent required version to 1.1 (and update ftp
site).
Problem reported by Magnus.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/360429e1d17947c17659cd57dbaaba5c10fcbd6a
Bruce Momjian wrote:
> Fix pg_bsd_indent bug where newlines were not being trimmed from typedef
> lines. Update pg_bsd_indent required version to 1.1 (and update ftp
> site).
>
> Problem reported by Magnus.
Oh, I also pgindented the file Magnus needed indented that led to this
report.
-
Improve planner's ability to recognize cases where an IN's RHS is unique.
If the right-hand side of a semijoin is unique, then we can treat it like a
normal join (or another way to say that is: we don't need to explicitly
unique-ify the data before doing it as a normal join). We were recognizing
Typo fixes.
expect -> except, noted by Andrew Dunstan. Also, "cannot" seems more
readable here than "can not", per David Wheeler.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/8be47f79d3a7d7bdb4a8c60d3f6055f3bc43ee4c
Modified Files
--
doc/src/s
Typo fixes.
expect -> except, noted by Andrew Dunstan. Also, "cannot" seems more
readable here than "can not", per David Wheeler.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/bf82013631e32436c9abb23fee8be0a4ce46b3dd
Modified Files
--
doc/src/sgml/fun
17 matches
Mail list logo