On Tue, Mar 20, 2018 at 3:36 PM, Andrew Dunstan
wrote:
> On Fri, Mar 2, 2018 at 8:27 AM, Alexander Korotkov
> wrote:
>> On Fri, Mar 2, 2018 at 12:40 AM, Nikita Glukhov
>> wrote:
>>>
>>> On 28.02.2018 06:55, Robert Haas wrote:
>>>
On Mon, Feb 26, 2018 at 10:34 AM, Nikita Glukhov
wrote:
On Fri, Mar 16, 2018 at 10:53 AM, Michael Paquier
wrote:
> On Tue, Mar 13, 2018 at 05:04:04PM +0900, Michael Paquier wrote:
> > Instead of doing what you are suggesting, why not moving
> > InitXLogInsert() out of InitXLOGAccess() and change InitPostgres() so as
> > the allocations for WAL inserts
Andrew Dunstan writes:
>> That seems like a quite limited list of functions. What about
>> reworking them providing a way of calling them without risk of
>> exception?
> I haven't seen a response to this email. Do we need one before
> proceeding any further with jsonpath?
I've not been followin
On Tue, Mar 20, 2018 at 10:43:55AM +0530, Dilip Kumar wrote:
> I think like WALWriterProcess, we need to call InitXLogInsert for the
> CheckpointerProcess as well as for the BgWriterProcess
> because earlier they were calling InitXLogInsert while check
> RecoveryInProgress before inserting the WAL.
On Tue, Mar 13, 2018 at 03:25:39PM -0400, Peter Eisentraut wrote:
> After more digging, there are more problems with having a bool that is
> not 1 byte. For example, pg_control has a bool field, so with a
> different bool size, pg_control would be laid out differently. That
> would require changi
Michael Paquier writes:
> On Tue, Mar 13, 2018 at 03:25:39PM -0400, Peter Eisentraut wrote:
>> So I'm going back to my proposal from December, to just use stdbool.h
>> when sizeof(bool) == 1, and add a static assertion to prevent other
>> configurations.
> So, on one side of the ring, we have mor
On Tue, Mar 20, 2018 at 11:26 AM, Michael Paquier
wrote:
> On Tue, Mar 20, 2018 at 10:43:55AM +0530, Dilip Kumar wrote:
> > I think like WALWriterProcess, we need to call InitXLogInsert for the
> > CheckpointerProcess as well as for the BgWriterProcess
> > because earlier they were calling InitXL
Hi,
Long transactions often annoy users because if a long transaction
exists on a database vacuum cannot reclaim efficiently. There are
several reason why they exist on a database but it's a common case
where users or applications forget to commit/rollback transactions.
That is, transaction is not
On 2018/03/19 20:25, Amit Langote wrote:
> That's all I have for now.
While testing this patch, I noticed a crash when performing EXPLAIN on
update of a partition tree containing foreign partitions. Crash occurs in
postgresEndForeignRouting() due to the following Assert failing:
Assert(fmstate
101 - 109 of 109 matches
Mail list logo