On Sun, Feb 5, 2023 at 3:05 PM Erik Wienhold wrote:
> > On 05/02/2023 23:17 CET Richard Brockie
> wrote:
> >
> > I maintain a Django webapp that uses postgresql and can create
> inefficient
> > queries if I'm not careful. I'm looking for ways to mimic a congested db
> > server in development to
Dionisis Kontominas writes:
>1. Regarding the different languages in the same column, that is normal
>if the column is a UTF-8 one, i.e. should be able to hold for example
>English, Greek and Chinese characters. In this case what is the best
>approach to define the collation and l
On Sun, Feb 5, 2023 at 4:19 PM Tom Lane wrote:
> If there's a predominant language in the data, selecting a collation
> matching that seems like your best bet. Otherwise, maybe you should
> just shrug your shoulders and stick with C collation. It's likely
> to be faster than any alternative.
FW
Because if I don't specify the collation/lctype it seems to get the default
from the OS, which in my case is : English_Netherlands.1252 (database
encoding UTF8). That might not be best for truly unicode content columns,
so I investigated the "C" option, which also seems not to work; might be
worse
Why are you specifying the collation to be "C" when the default db encoding
is UTF8, and UTF-8 has Greek, Chinese and English encodings?
On 2/5/23 17:08, Dionisis Kontominas wrote:
Hello all,
I have a question regarding the definition of the type of a character
field in a table and more spe
Hi Tom,
1. Regarding the different languages in the same column, that is normal
if the column is a UTF-8 one, i.e. should be able to hold for example
English, Greek and Chinese characters. In this case what is the best
approach to define the collation and lctype of the column? Either
Dionisis Kontominas writes:
>I suppose that affects the outcome of ORDER BY clauses on the field,
> along with the content of the indexes. Is this right?
Yeah.
>Assuming that the requirement exists, to store UTF-8 characters on a
> field that can be from multiple languages, and the datab
Hello Tom,
Thank you for your response.
I suppose that affects the outcome of ORDER BY clauses on the field,
along with the content of the indexes. Is this right?
Assuming that the requirement exists, to store UTF-8 characters on a
field that can be from multiple languages, and the data
Dionisis Kontominas writes:
> Let's say that the definition is for example as follows:
> name character varying(8) COLLATE pg_catalog."C" NOT NULL
> and also assume that the database default encoding is UTF8 and also the
> Collate and Ctype is "C"". I plan to store strings of various languag
Hello all,
I have a question regarding the definition of the type of a character
field in a table and more specifically about its collation and UTF-8
characters and strings.
Let's say that the definition is for example as follows:
name character varying(8) COLLATE pg_catalog."C" NOT NULL
> On 05/02/2023 23:17 CET Richard Brockie wrote:
>
> I maintain a Django webapp that uses postgresql and can create inefficient
> queries if I'm not careful. I'm looking for ways to mimic a congested db
> server in development to expose these queries.
pgbench is what your looking for:
https://ww
Hi,
I maintain a Django webapp that uses postgresql and can create inefficient
queries if I'm not careful. I'm looking for ways to mimic a congested db
server in development to expose these queries.
The configuration of postgresql is complicated - is there a simple method
by which I could, for ex
12 matches
Mail list logo
