> The first thing that comes to mind for me is fsync working correctly (i.e.
> actually waiting for the disk write) in Linux but not in Windows.
> On a weird VM stack like you've got, it's not hard for that sort of thing to
> go
> wrong. Needless to say, if that's the issue then the apparent perf
David Rowley writes:
> On Fri, 4 Jun 2021 at 23:53, Taras Savchuk wrote:
>> Any ideas what's wrong? For me such a big difference on identical
>> databases/queries looks strange.
> It's pretty difficult to say. You've not provided any useful details
> about the workload you're running.
> If this
also if you can setup an external timer \timing , along with explain
analyse to get total time, it would help if everything else is same.
I have seen some threads thar mention added startup cost for parallel
workers on windows but not on Linux.
But I do not want to mix those threads here, but jus
On Fri, 4 Jun 2021 at 23:53, Taras Savchuk wrote:
> My real life test is to "register" 10 _same_ documents (провести документы)
> in each of 1C/PostgreSQL DBs. Both PostgreSQL DBs are identical and just
> before test imported to PostgreSQL via application server (DT import).
> On Windows Server
