On Sat, Jul 01, 2023 at 01:40:49AM -0400, Kirk Wolak wrote:
>
> FWIW, I discovered that psql is case sensitive on the dbname, without
> quoting it!
That's on purpose, since shell quoting behavior is entirely different from SQL.
The quotes are discarded by the shell, so it would otherwise require u
On Fri, Jun 30, 2023 at 8:39 AM wrote:
> On Fri, 30 Jun 2023 11:16:36 +0800 Julien Rouhaud wrote:
>
> >Hi,
> >
> >On Thu, Jun 29, 2023 at 10:42:00PM -0400, p...@pfortin.com wrote:
> >>
> >> Windows: %APPDATA%\postgresql\pgpass.conf
> >>
>
> echo %APPDATA%
> C:\Users\Pierre\AppData\Roaming
>
> >
Over in pgsql-hackers, I've proposed removing the db_user_namespace
parameter in v17 [0]. I am personally not aware of anyone using this
parameter, but I wanted to give folks an opportunity to object in case they
are using it (or are aware of someone who is).
[0] https://postgr.es/m/2023063020050
On Fri, 2023-06-30 at 17:06 +, Chandy G wrote:
> For instance : Can the postgres internal component (wal-sender / *)
> interpret this special
> toasted-col-value sitting in the wal-file -> replace it with the actual value
> and send it to
> the replication slot.
Which logical decoding plugi
Hi PG Users, We are running into the postgres toasted values showing up in
replication slots. We are using debezium and have gone through the following
1. Various options for handling toasted values during replication at the
application level.2. Postgres option to turn on replica identitiy to fu
On Thu, 29 Jun 2023 20:27:59 -0700 David G. Johnston wrote:
>On Thu, Jun 29, 2023 at 7:42 PM wrote:
>
>> Trying to write a script that will run on Linux, Windows, and Mac.
>>
>
>This seems impossible on its face unless you use WSL within the Windows
>environment. And if you are doing that, the
On Fri, 30 Jun 2023 11:16:36 +0800 Julien Rouhaud wrote:
>Hi,
>
>On Thu, Jun 29, 2023 at 10:42:00PM -0400, p...@pfortin.com wrote:
>>
>> Windows: %APPDATA%\postgresql\pgpass.conf
>>
>> On Linux, this works. However, on Windows, psql will not read
>> pgpass.conf (tried in just about every location
Hi,
On Fri, Jun 30, 2023 at 01:47:29PM +0530, Ashok Patil wrote:
> Hello MAZIÈRE,
>
> I tried update by
>
> listen_addresses = '*' and listen_addresses = 'server_address' but still
> i am getting same error.
Did you restart postgres after changing listen_addresses, and is the primary
port 5432?
Hello MAZIÈRE,
I tried update by
listen_addresses = '*' and listen_addresses = 'server_address' but still
i am getting same error.
Searched on internet for probable solution but does not get any proper
answer.
Will you please reply me for this issue?
Regards,
Ashok
On Tue, Jun 27, 2023 at
