>
>
> Is anybody able spotting, what am I doing wrong here? Thank you
>
Unless I'm mistaken, it seems like you are trying to run jetty and postgres
in the same container. You should really use two containers and run them
both with docker compose. Docker is very much designed to run a single
ser
Thank you Torsten,
On Mon, Dec 2, 2024 at 12:32 PM Torsten Krah wrote:
> Am Sonntag, dem 01.12.2024 um 21:59 +0100 schrieb Alexander Farber:
> > But I am yet not sure how to enable listening at localhost again
>
> Instead of using a TCP/IP connection, why not use the unix socket to
> connect to
Hi again, I would like to share a slightly better workaround
(does not restart PostgreSQL) for enabling localhost connections
(for example for servlets) in a postgres:17-alpine3.20 based Dockerfile:
RUN sed -i "s/listen_addresses=''/listen_addresses='localhost'/"
/usr/local/bin/docker-entrypoint.s
Am Sonntag, dem 01.12.2024 um 21:59 +0100 schrieb Alexander Farber:
> But I am yet not sure how to enable listening at localhost again
Instead of using a TCP/IP connection, why not use the unix socket to
connect to your database [1]?
[1] https://jdbc.postgresql.org/documentation/use/#unix-sockets
TeamPl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver
15.X
Env = EC2 based Community PostgreSQL Ver 13.16.2
we will be performing upgrade of our EC2 server too along with new OS.
Need help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
ASIS-exis
On 12/2/24 14:18, Bharani SV-forum wrote:
Team
Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver
15.X
Env = EC2 based Community PostgreSQL Ver 13.16.2
we will be performing upgrade of our EC2 server too along with new OS.
Need help in vetting my steps for Postgres DB u
On 12/2/24 14:31, Ron Johnson wrote:
On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum
mailto:esteembsv-fo...@yahoo.com>> wrote:
Team
Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
ver 15.X
Env = EC2 based Community PostgreSQL Ver 13.16.2
we will be per
On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum
wrote:
> Team
> Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver
> 15.X
>
> Env = EC2 based Community PostgreSQL Ver 13.16.2
>
> we will be performing upgrade of our EC2 server too along with new OS.
>
> Need help in vetting
On 12/2/24 14:46, Adrian Klaver wrote:
On 12/2/24 14:31, Ron Johnson wrote:
On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum
mailto:esteembsv-fo...@yahoo.com>> wrote:
Team
Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
ver 15.X
Env = EC2 based Community Po
On 12/1/24 12:15, Tom Lane wrote:
Cool. You did actually install the new scripts into your target
installation, right?
Oh, is applying the patch and rebuilding PostgreSQL not enough?
Ron/AdrianThanks for your input.Your suggestion is
option#1 ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*-
ensure to capture all the pre.req meant for ver 15.10 are being met.
- enable logical replication tagged to proposed new EC2 server (with newer
Higher OS Version
On 12/2/24 15:41, Bharani SV-forum wrote:
Ron/Adrian
Thanks for your input.
Your suggestion is
*option#1*
ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
- ensure to capture all the pre.req meant for ver 15.10 are being met.
- enable logical replication tagged to prop
Adrian
Proposed new Server is intended to have higher OS Version (centos ver 9.0) and
higher Postgres Version 15.10
Does logical replication will have issues , if the existing asis server is
having Postgres ver 13.16.2 with Cent Os 7.0 with the new server having higher
OS version Centos Ver 9.0
Hello,
I encountered an issue while attempting to reclaim space from a heavily bloated
table:
Initial analysis using
https://github.com/ioguix/pgsql-bloat-estimation/blob/master/table/table_bloat.sql
indicated approximately 600GB of bloat in the table.
I initiated a VACUUM FULL operation to r
On 12/2/24 15:52, Bharani SV-forum wrote:
Adrian
Proposed new Server is intended to have higher OS Version (centos ver
9.0) and higher Postgres Version 15.10
Alright I did not catch this " ... with new OS" from your original post.
I saw "Take offline full backup (PG_DATA folder alone) using
On 2024-12-03 00:25:15 +, Bharani SV-forum wrote:
> qsn1: What is the size of database(s) you are dealing with?
> ans1: roughly 25 GB (maximum size)
>
> qsn2 : What sort of downtime can you afford?
> ans2: can be maximum 30 mins or so
That does seem sufficient time to dump/restore a 25 GB da
Adrian,
OP is moving to a new VM when migrating to PG 15. When was the
"cross-server" feature added to pg_upgrade?
On Mon, Dec 2, 2024 at 5:48 PM Adrian Klaver
wrote:
> On 12/2/24 14:46, Adrian Klaver wrote:
> > On 12/2/24 14:31, Ron Johnson wrote:
> >> On Mon, Dec 2, 2024 at 5:18 PM Bharani S
Hi,
Le mar. 3 déc. 2024, 01:02, Pierre Barre a écrit :
> Hello,
>
> I encountered an issue while attempting to reclaim space from a heavily
> bloated table:
>
> Initial analysis using
> https://github.com/ioguix/pgsql-bloat-estimation/blob/master/table/table_bloat.sql
> indicated
> approximate
PopeRigby writes:
> On 12/1/24 12:15, Tom Lane wrote:
>> Cool. You did actually install the new scripts into your target
>> installation, right?
> Oh, is applying the patch and rebuilding PostgreSQL not enough?
Not unless you did "make install" in the contrib/earthdistance
directory (or somethi
AdrianNoted about, Logical replication would not have issue with this as that
is one of
it's use cases.
qsn1: What is the size of database(s) you are dealing with?
ans1: roughly 25 GB (maximum size)
qsn2 : What sort of downtime can you afford?
ans2: can be maximum 30 mins or so
qsn3: EC2 --> E
On 12/2/24 17:23, Ron Johnson wrote:
Adrian,
OP is moving to a new VM when migrating to PG 15. When was the
"cross-server" feature added to pg_upgrade?
Moving to a new VM was not the issue, my mistake was thinking the OS
version was staying the same.
Then:
On old VM:
"take offline ful
21 matches
Mail list logo
