Re: How to do faster DML - Mailing list pgsql-general

From veem v
Subject Re: How to do faster DML
Date
Msg-id CAB+=1TVP9xFM16J_ipQaL05UYQPAYyP51xzOSnvcmppBLKvYpA@mail.gmail.com
Whole thread Raw
In response to Re: How to do faster DML  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
Responses Re: How to do faster DML  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: How to do faster DML  (Ron Johnson <ronljohnsonjr@gmail.com>)
Re: How to do faster DML  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
List pgsql-general

On Sun, 11 Feb 2024 at 19:02, Peter J. Holzer <hjp-pgsql@hjp.at> wrote:
> Similarly for Number/Numeric data type.

Number in Oracle and numeric in PostgreSQL are variable length types.
But in PostgreSQL you also have a lot of fixed length numeric types
(from boolean to bigint as well as float4 and float8) and you would
normally prefer those over numeric (unless you really need a decimal or
very long type). So padding is something you would encounter in a
typical PostgreSQL database while it just wouldn't happen in a typical
Oracle database.


When you said "you would normally prefer those over numeric " I was thinking the opposite. As you mentioned integer is a fixed length data type and will occupy 4 bytes whether you store 15 or 99999999.But in case of variable length type like Number or numeric , it will resize itself based on the actual data, So is there any downside of going with the variable length data type like Numeric, Varchar type always for defining the data elements?

Regards
Veem

pgsql-general by date:

Previous
From: Justin
Date:
Subject: Re: Partitioning options
Next
From: "David G. Johnston"
Date:
Subject: Re: How to do faster DML