Grega Jesih writes:
> It matters a lot. It means time saving. Plenty of time. So we're talking
> performance. Not postgres performance, interface performance.
One more time: our docs are here to explain Postgres performance.
It is very easy to show that char/varchar are strictly worse than
text
On Wed, Nov 3, 2021 at 11:09 AM Grega Jesih
wrote:
> The new architectures include more and more data exchange among databases.
> Now when you deal with bigger data sizes that go from millions to
> billions, this fixed size vs of text - undefined size becomes very
> relevant.
>
Can you demonstrat
Dear Tom and David,
>I'll just point out in passing, though, that "fixed record size" for text
>strings is an illusion as soon as you have to deal with non-ASCII data.
>So I'm skeptical that such optimizations are worth much anymore.
It doesn't matter is it ascii or not. A string is a string. A
Grega Jesih writes:
>> The goal in our docs is to point out that using an arbitrary length
>> specification is not required in PostgreSQL.
> Well perhaps yours. But there are pro-tools (I refer to SSIS in this context)
> that provide a very fast dataflow in case there is a known record size.
T
Dear David,
> The goal in our docs is to point out that using an arbitrary length
> specification is not required in PostgreSQL.
Then it should say so. Because unexperienced reader then uses this limited
focus and generalizes.
It is for the very same reason that progreammers don't perceive the n
On Wed, Nov 3, 2021 at 8:35 AM Grega Jesih wrote:
> Dear David,
>
> > The goal in our docs is to point out that using an arbitrary length
> specification is not required in PostgreSQL.
>
> Then it should say so. Because unexperienced reader then uses this limited
> focus and generalizes.
>
It do
On Wed, Nov 3, 2021 at 6:55 AM PG Doc comments form
wrote:
> But performance in ETL processes related to such data type is decreased
> dramatically, because any process that takes this kind of data needs to
> calculate its size on a row level and cannot take bigger chunks of data
> based on max s
On Wed, Nov 3, 2021 at 01:29:19PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/datatype-character.html
> Description:
>
> Text field is a field that is intended for very big texts.
> Perfor
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/datatype-character.html
Description:
Text field is a field that is intended for very big texts.
Performance within Postgres database is commented to be the same as for
normal varchar.
