Peter Eisentraut writes:
> On 10.10.23 08:22, Laurenz Albe wrote:
>> Apart from that, it is a good idea to use table names that are standard
>> SQL identifiers, so that you don't have to double quote them all the time.
> FWIW, the Chinese character sequences posted here would be valid
> unquote
On 10.10.23 08:22, Laurenz Albe wrote:
Apart from that, it is a good idea to use table names that are standard
SQL identifiers, so that you don't have to double quote them all the time.
FWIW, the Chinese character sequences posted here would be valid
unquoted identifiers if PostgreSQL implemen
Hello.
We had PostgreSQL v11 and used PITR with our database.
But PITR behavior was changed in v13
>https://www.postgresql.org/docs/release/13.0/
>Generate an error if recovery does not reach the specified recovery target
>(Leif Gunnar Erlandsen, Peter Eisentraut)
>Previously, a standby would pro
Laurenz Albe writes:
> On Tue, 2023-10-10 at 15:53 +0900, Tatsuo Ishii wrote:
>> Another solution would be, letting the meaning of NAMEDATALEN to be
>> number of *characters*, not the number of bytes. This way, you can use
>> up to 64 UTF-8 characters. In my understanding MySQL already does this
>
On Tue, 2023-10-10 at 15:53 +0900, Tatsuo Ishii wrote:
> Another solution would be, letting the meaning of NAMEDATALEN to be
> number of *characters*, not the number of bytes. This way, you can use
> up to 64 UTF-8 characters. In my understanding MySQL already does this
> way. I know this requires
