to give the user control over the expected file transfer
> performance. Here, I have added this checksum rewriting to the existing
> --copy mode, and I have measured about a 5% overhead. An alternative
> would be to make this an explicit mode (--copy-slow,
> --copy-and-make-adjustments).
Maybe a separate -k flag to enable this behavior explicitly?
best regards,
Ilya
--
Ilya Kosmodemiansky
CEO, Founder
Data Egret GmbH
Your remote PostgreSQL DBA team
T.: +49 6821 919 3297
i...@dataegret.com
Hi,
> On 28. Nov 2023, at 06:41, Wirch, Eduard wrote:
>
>
>
> :
>
> ERROR: could not serialize access due to read/write dependencies among
> transactions
> Detail: Reason code: Canceled on identification as a pivot, with conflict
> out to old committed transaction 61866959.
>
> There is
> On 14. Sep 2018, at 16:31, Ilya Kosmodemiansky wrote:
>
>
>
>
> I could only heavily +1 this. I can get
I can’t get of course, sorry for typo
> from where comes the idea that community is only what happens just on
> postgresql.org or just on some othe
> On 14. Sep 2018, at 16:17, Dave Page wrote:
>
>
> The lists are just one of many different ways people in this community
> interact.
I could only heavily +1 this. I can get from where comes the idea that
community is only what happens just on postgresql.org or just on some other
channel
On Fri, Sep 14, 2018 at 10:31 AM, Chris Travers wrote:
> I really have to object to this addition:
> "This Code is meant to cover all interaction between community members,
> whether or not it takes place within postgresql.org infrastructure, so long
> as there is not another Code of Conduct that
