* Michael Paquier (michael.paqu...@gmail.com) wrote:
> On Wed, Jan 18, 2017 at 7:31 AM, Stephen Frost wrote:
> > Perhaps we need a way for pg_ctl to realize a cold-standby case and
> > throw an error or warning if --wait is specified then, but that hardly
> > seems
On Tue, Jan 17, 2017 at 11:27 PM, Robert Haas wrote:
> On Mon, Jan 16, 2017 at 7:11 AM, Amit Kapila wrote:
> WAIT_EVENT_PARALLEL_INDEX_SCAN is in fact btree-specific. There's no
> guarantee that any other AMs the implement parallel index scans
Peter Eisentraut writes:
> Generate fmgr prototypes automatically
BTW, I notice some suspicious-looking behavior with -j:
$ make -j8 -s
On Wed, Jan 18, 2017 at 8:15 PM, Vladimir Rusinov wrote:
> On the topic of binaries, there's going to be another patch renaming them.
> Those will have no aliases as it's trivial to work-around (symlinks, shell
> scripts, etc) and not so trivial to implement in a portable
Sorry for the broken formatting in my previous message.
Below is a corrected version of this message.
I'd like to present a series of patches that implements k-Nearest Neighbors
(kNN) search for btree, which can be used to speed up ORDER BY distance
queries like this:
SELECT * FROM events ORDER
On Wed, Jan 18, 2017 at 8:18 AM, Etsuro Fujita
> On 2017/01/16 11:38, Etsuro Fujita wrote:
>> On 2017/01/14 6:39, Jeff Janes wrote:
>>> I do get a compiler warning:
>>> foreign.c: In function 'CreateLocalJoinPath':
>>> foreign.c:832: warning:
On Tue, Jan 17, 2017 at 10:03 PM, Robert Haas wrote:
> Q: OK, where is my WAL stored?
> A: pg_wal
> Q: How do I reset it?
> A: pg_resetxlog
On the topic of binaries, there's going to be another patch renaming them.
Those will have no aliases as it's trivial to
On Fri, Jan 6, 2017 at 6:58 PM, Ashutosh Sharma wrote:
I've successfully applied the patch on the latest head and ran a
regression tests without any failure. There is no major changes.
However, I've some minor comments on the patch:
+ * HASH_ALLOCATABLE_PAGE_SZ
On Wed, Jan 4, 2017 at 5:36 PM, Merlin Moncure wrote:
> Still getting checksum failures. Over the last 30 days, I see the
> following. Since enabling checksums FWICT none of the damage is
> permanent and rolls back with the transaction. So creepy!
The checksums still
> +static Page
> +verify_hash_page(bytea *raw_page, int flags)
> Few checks for meta page are missing, refer _hash_checkpage.
okay, I have added the checks for meta page as well. Please refer to
> + if (!superuser())
> + ereport(ERROR,
(I apologize in advance for possible inaccurate wording on maths,
which might cause confusion..)
At Wed, 11 Jan 2017 16:37:59 +0100, Emre Hasegeli wrote in
> > - Floating point comparisons for
101 - 111 of 111 matches
Mail list logo