Hi,
I was wondering why psql loose dashed comments and what can be done about this
misbehaviour.
I get often some sql, paste it into psql run and edit it via \e. A few
iterations until everything works.
But psql removes the comments and creates a lot extra work to restore the
comments and chan
> I was wondering why psql loose dashed comments and what can be done about
> this misbehaviour.
>
> postgres=# \e
>
>
> Because \e treats the query buffer as a single line of code and dashed
> comments cannot be used, just like meta-commands cannot be used.
>
> Including a filename should es
> Am 17.03.2023 um 08:56 schrieb Andreas Joseph Krogh :
>
> Hi, in PG-14, how do I delete the keys "dunsNumber": "NaN":
>
> {
> "sessionId": "ce6fc9d0-5923-4d71-9f7e-ae60f35c45d6",
> "details": [
> {
> "keyInformation": {
> "dunsNumber": "NaN",
> "organizationType
Hi Matt,
>
> 1. What do the double parenthesis '(( Values ))' mean?
Nothing, it was easier to continue typing and close one more on the phone.
Single parenthesis are enough.
>
> 2. What is the 'x(field)' in the column alias?
X(field) is just to make the example more readable. And name
Hi there,
I think you can use -T 3600 -D If you don't want to kill the backends.
--
Boris
> Am 19.01.2025 um 13:52 schrieb nicolas75...@yahoo.fr:
>
> Hi
>
> Thanks for the help but this will not help, killing other process is not safe
> The good way will be that pg_repack tools include a ti
