On Sun, 1 Sept 2024 at 10:03, veem v wrote:
>
> On Sun, 1 Sept 2024 at 09:13, David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>> On Saturday, August 31, 2024, veem v wrote:
>>
>>>
>>>
>>> iii)And then alter the datatype of the partition key transaction_date to
>>> DATE in one shot at
On Sun, 1 Sept 2024 at 09:13, David G. Johnston
wrote:
> On Saturday, August 31, 2024, veem v wrote:
>
>>
>>
>> iii)And then alter the datatype of the partition key transaction_date to
>> DATE in one shot at the table level(which should be fast as its having more
>> granularity as compare to exi
On Saturday, August 31, 2024, veem v wrote:
>
> 1) if it's technically possible to have a unique key on only the
> transaction_id column having the partition key on the
> transaction_timestamp, because the table is going to be queried/purged
> based on the transaction_timestamp?
>
There is prese
On Sun, 1 Sept 2024 at 03:58, Adrian Klaver
wrote:
>
> The model is at odds with itself and untenable. If the tables hold
> multiple rows for a given transaction_id then you cannot have a
> PK/Unique constraint on that column. Seems there is a decided lack of
> any planning. The only way I can s
On 2024-09-01 02:54, Peter J. Holzer wrote:
'Tis the season again.
Ubuntu 24.04.1 has just been released, so many Ubuntu LTS users will
now
be prompted to upgrade from 22.04 to 24.04.
A word of warning to those who use Postgresql from the Ubuntu repo (not
PGDG):
As usual, a newer Ubuntu vers
On 8/31/24 13:02, veem v wrote:
Hello,
We have our transaction tables daily range partitioned based on
transaction_timestamp column which is timestamptz data type and these
are having composite primary key on (transaction_id,
transaction_timestamp). And we were using an "insert on conflict" f
Hello,
We have our transaction tables daily range partitioned based on
transaction_timestamp column which is timestamptz data type and these are
having composite primary key on (transaction_id, transaction_timestamp).
And we were using an "insert on conflict" for loading data to our system ,
which
On 2024-08-31 10:35:01 -0700, Adrian Klaver wrote:
> On 8/31/24 09:54, Peter J. Holzer wrote:
> > 'Tis the season again.
> >
> > Ubuntu 24.04.1 has just been released, so many Ubuntu LTS users will now
> > be prompted to upgrade from 22.04 to 24.04.
>
> Which I ignore.
At some point I do want to
On 8/31/24 09:54, Peter J. Holzer wrote:
'Tis the season again.
Ubuntu 24.04.1 has just been released, so many Ubuntu LTS users will now
be prompted to upgrade from 22.04 to 24.04.
Which I ignore.
A word of warning to those who use Postgresql from the Ubuntu repo (not
PGDG):
Why I do use
'Tis the season again.
Ubuntu 24.04.1 has just been released, so many Ubuntu LTS users will now
be prompted to upgrade from 22.04 to 24.04.
A word of warning to those who use Postgresql from the Ubuntu repo (not
PGDG):
As usual, a newer Ubuntu version comes with a newer Postgres version (16
inst
10 matches
Mail list logo
