On Fri, 2021-11-05 at 11:27 -0400, Bruce Momjian wrote:
> On Fri, Nov 5, 2021 at 07:32:12AM -0700, David G. Johnston wrote:
> > On Friday, November 5, 2021, Bruce Momjian wrote:
> >
> >
> > >
> > > Perhaps, right before the tip you quoted, something like that:
> > >
> > > If
On Fri, Nov 5, 2021 at 07:32:12AM -0700, David G. Johnston wrote:
> On Friday, November 5, 2021, Bruce Momjian wrote:
>
>
> >
> > Perhaps, right before the tip you quoted, something like that:
> >
> > If your use case requires a length limit on character data, or
>
On Friday, November 5, 2021, Bruce Momjian wrote:
>
> >
> > Perhaps, right before the tip you quoted, something like that:
> >
> > If your use case requires a length limit on character data, or
> compliance
> > with the SQL standard is important, use "character varying".
> > Otherwise, you
On 2021-Oct-26, nikolai.berkoff wrote:
> Given all the suggestions I've tried to combine them into one patch again.
OK, I pushed something very similar but not exactly your patch ...
please have a look if you care to suggest improvements.
... oh, I just noticed I made a typo -- omitted "with"
On Fri, Nov 5, 2021 at 03:15:35PM +0100, Laurenz Albe wrote:
> On Fri, 2021-11-05 at 09:51 +, Grega Jesih wrote:
> > Suggested current text addendum:
> >
> > But, if you consider doing ETL from Postgres database to some outer target
> > environment and you seek performance in such
On Fri, 2021-11-05 at 09:51 +, Grega Jesih wrote:
> Suggested current text addendum:
>
> But, if you consider doing ETL from Postgres database to some outer target
> environment and you seek performance in such interfaces, follow the logic
> of limited size (varchar or char) data types in
Hi David.
> We’re entitled to a bit of self-centeredness here, especially when the
> broader world is so varied
One can tell ;-)
Current text:
[cid:image001.png@01D7D233.09B9B710]
Suggested current text addendum:
But, if you consider doing ETL from Postgres database to some outer target
