Hi,
I have a question about logical decoding of Postgres.
where are the entry points to logical decoding?
Specifically, we want to know whether logical decoding happens immediately
after commit, or whether there is a polling thread that scans the Write
Ahead Log and then dumps to the special t
Fix TAP tests and MSVC scripts for pathnames with spaces.
Change assorted places in our Perl code that did things like
system("prog $path/file");
to do it more like
system('prog', "$path/file");
which is safe against spaces and other special characters in the path
variable. The la
Fix TAP tests and MSVC scripts for pathnames with spaces.
Change assorted places in our Perl code that did things like
system("prog $path/file");
to do it more like
system('prog', "$path/file");
which is safe against spaces and other special characters in the path
variable. The la
Fix TAP tests and MSVC scripts for pathnames with spaces.
Change assorted places in our Perl code that did things like
system("prog $path/file");
to do it more like
system('prog', "$path/file");
which is safe against spaces and other special characters in the path
variable. The la
Peter Eisentraut writes:
> On 7/8/16 12:01 PM, Tom Lane wrote:
>> Add some temporary code to record stack usage at server process exit.
> In spite of the void cast, this is still warning
> ipc.c:125: ignoring return value of âsystemâ, declared with attribute
> warn_unused_result [-Wunused-r
Improve recording of IA64 stack data.
Examination of the results from anole and gharial suggests that we're
only managing to track the size of one of the two stacks of IA64 machines.
Some googling gave the answer: on HPUX11, the register stack is reported
as a page type I don't see in pstat.h on m
On 7/8/16 12:01 PM, Tom Lane wrote:
Add some temporary code to record stack usage at server process exit.
In spite of the void cast, this is still warning
ipc.c:125: ignoring return value of ‘system’, declared with attribute
warn_unused_result [-Wunused-result]
--
Peter Eisentraut
On 7/2/16 11:22 AM, Bruce Momjian wrote:
doc: mention dependency on collation libraries
Document that index storage is dependent on the operating system's
collation library ordering, and any change in that ordering can create
invalid indexes.
I think you're missing some punctuation between "No
