On Thu, 2020-10-15 at 17:22 +, Raj Iyer wrote:
> Is there information available on what versions of Postgres are certified and
> supported on what Operating System platforms.
There is no certification; you are stuck in closed source land.
Here is a list of operating systems that are supporte
On Thu, 2020-10-15 at 20:58 +, Dirk Krautschick wrote:
> because of a migration from DB2 we have a lot of timestamps like
>
> -12-31-00.00.00.00
>
> What would be the best way to handle this in Postgres also related
> to overhead and performance (index usage?).
>
> Or is
>
> TO_TIM
Thank you Michael for your suggestion,
I will reduce vacuum_cost_delay and increasing vacuum_cost_limit to speedup
vacuum.
But the I/O system is very solicitated on PROD system and I do not want to
impact end user performance.
If aggressive cost_delay and vacuum_cost_limit slow down significative
Greetings,
* Christophe Pettus (x...@thebuild.com) wrote:
> > On Oct 15, 2020, at 13:49, Dirk Krautschick
> > wrote:
> > Or do you have some other ideas how to use a primary key datatype like UUID
> > but with variable length?
>
> You're probably best off storing it as a VARCHAR() with a check
On 2020-Oct-15, Dirk Krautschick wrote:
> Hi,
>
> I have here a situation with the usage of UUID. Here the database user
> allows UUIDs with less then 16 byte lengths (please don't ask :-) ).
>
> Of course there are some technical ways to do the filling of the not
> used bytes but I hope there i
