pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Wilm Hoyer <W.Hoyer@dental-vision.de>
To: Pavel Biryukov <79166341370@yandex.ru>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: AW: AW: posgres 12 bug (partitioned table)
Date: Wed, 12 Aug 2020 10:57:49 +0000
Message-ID: <05311413c04d49d8be4dd4a21ad587fc@dental-vision.de> (raw)
In-Reply-To: <95271597226022@mail.yandex.ru>
References: <141051591267657@mail.yandex.ru>
	<1251598.1591289850@sss.pgh.pa.us>
	<CA+TgmoaN0kQa3nxToHtD8nRymSnUYaj4XL3zKq8Q_0AUJcQNPQ@mail.gmail.com>
	<3398357.1597160032@sss.pgh.pa.us>
	<1058041597161586@mail.yandex.ru>
	<20200811172241.izeyvksgevbtvhcd@alap3.anarazel.de>
	<24981597170121@mail.yandex.ru>
	<20200811183940.z6hvnu4uptkhugom@alap3.anarazel.de>
	<52371597219372@mail.yandex.ru>
	<0765c3d6a42b4aa182febf866b5ab338@dental-vision.de>
	<95271597226022@mail.yandex.ru>


> Wilm,

> Have a look, there is even an extension method for xmin (stable branch):

> https://github.com/npgsql/efcore.pg/blob/stable/src/EFCore.PG/Extensions/NpgsqlEntityTypeBuilderExte...

> EF Core is mostly independent from DB, but there usually are some "tweaks" for each database that you should know (like for SQL server the native concurrency token should be like byte[]:

  1.  [TimeStamp]
  2.  public byte[] RowVersion { get; set; }
  3.  )

> Additional "self defined column" for billion rows tables leads to additional space needed. We use partitioning when the tables are LARGE :)

> This works fine in 10, 11, it's strange it is broken in 12 (from db users point of view, I haven't examined the sources of PG for internals...)

Sorry, i had not looked into the extension since it is not part of core npgsql. As it states: Npgsql.EntityFrameworkCore.PostgreSQL is an Entity Framework Core provider built on top of Npgsql<https://github.com/npgsql/npgsql;. (and we left npgsql before this extension was started).
I guess it would be easy for them to implement a solution, because that basically means adopting the relevant part from the EF SqlServer implementation. But i fear you’re out of luck with them, as support for table partitioning is still an open issue in their project.

Best regards
Wilm.


view thread (2+ messages)  latest in thread

Message-ID: <05311413c04d49d8be4dd4a21ad587fc@dental-vision.de>
Permalink:  ../05311413c04d49d8be4dd4a21ad587fc@dental-vision.de/
Also on:    postgresql.org/message-id/05311413c04d49d8be4dd4a21ad587fc@dental-vision.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: W.Hoyer@dental-vision.de, 79166341370@yandex.ru, andres@anarazel.de, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: AW: AW: posgres 12 bug (partitioned table)
  In-Reply-To: <05311413c04d49d8be4dd4a21ad587fc@dental-vision.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox