# PostgreSQL update fails from China
**URL:** https://meta.discourse.org/t/postgresql-update-fails-from-china/350869
**Category:** Support
**Created:** [February 6, 2025, 10:58am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869 "2025-02-06T10:58:57Z")
**Posts on this page:** 19
**Page:** 1
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 6, 2025, 4:59am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/1 "2025-02-06T04:59:11Z")
data cannot be rebuild
```plaintext
./launcher rebuild data
x86_64 arch detected.
Ensuring launcher is up to date
Launcher is up-to-date
2.0.20250129-0720: Pulling from docker-hub-china/discourse-base
Digest: sha256:d798a945ca4d31c29e5d263cdaf807bafab9b5f6737be0b1b852bea0063a3b91
Status: Image is up to date for registry.cn-wulanchabu.aliyuncs.com/docker-hub-china/discourse-base:2.0.20250129-0720
registry.cn-wulanchabu.aliyuncs.com/docker-hub-china/discourse-base:2.0.20250129-0720
/usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2025-02-06T04:49:43.809493 #1] INFO -- : Reading from stdin
I, [2025-02-06T04:49:43.812252 #1] INFO -- : Skipped missing before_code hook
I, [2025-02-06T04:49:43.812294 #1] INFO -- : Skipped missing before_db_migrate hook
I, [2025-02-06T04:49:43.812309 #1] INFO -- : Skipped missing after_code hook
I, [2025-02-06T04:49:43.816721 #1] INFO -- : File > /etc/service/postgres/run chmod: +x chown:
I, [2025-02-06T04:49:43.820580 #1] INFO -- : File > /etc/service/postgres/log/run chmod: +x chown:
I, [2025-02-06T04:49:43.824283 #1] INFO -- : File > /etc/runit/3.d/99-postgres chmod: +x chown:
I, [2025-02-06T04:49:43.827979 #1] INFO -- : File > /root/install_postgres chmod: +x chown:
I, [2025-02-06T04:49:43.832007 #1] INFO -- : File > /root/upgrade_postgres chmod: +x chown:
I, [2025-02-06T04:49:43.832273 #1] INFO -- : Replacing data_directory = '/var/lib/postgresql/15/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.832904 #1] INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.833313 #1] INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.843122 #1] INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.843548 #1] INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.843885 #1] INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.844162 #1] INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.844439 #1] INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.844732 #1] INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T04:49:43.845050 #1] INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres peer in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T04:49:43.845283 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T04:49:43.845505 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T04:49:43.845723 #1] INFO -- : > if [-f /root/install_postgres]; then
/root/install_postgres && rm -f /root/install_postgres
elif [-e /shared/postgres_run/.s.PGSQL.5432]; then
socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
fi
2025/02/06 04:49:45 socat[33] E connect(, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): Connection refused
initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
```
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [February 6, 2025, 5:31am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/2 "2025-02-06T05:31:29Z")
Your logs appear to be incomplete but the snippet below can provide a hint.
> socat[33] E connect(, AF=1 “/shared/postgres\_run/.s.PGSQL.5432”, 36): Connection refused
Are you also seeing the error below much lower in your log output?
> The source cluster was not shut down cleanly
If so, you can try following [these instructions](https://meta.discourse.org/t/postgresql-15-update/349515#p-1698209-the-source-cluster-was-not-shut-down-cleanly-10).
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 6, 2025, 5:46am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/3 "2025-02-06T05:46:23Z")
No containers are running
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [February 6, 2025, 5:48am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/4 "2025-02-06T05:48:16Z")
> [@PostgreSQL 15 update](https://meta.discourse.org/t/postgresql-15-update/349515/1):
>
> Restart the old container with `./launcher start app`. Wait a few minutes until it is back up.
Are you seeing any errors from that first step?
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 6, 2025, 5:49am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/5 "2025-02-06T05:49:58Z")
I used the data.yml and web\_only.yml methods
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [February 6, 2025, 5:52am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/6 "2025-02-06T05:52:23Z")
You can still follow the same instructions, but replace any occurrences of `app` or `standalone` with `data`.
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 6, 2025, 6:05am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/7 "2025-02-06T06:05:43Z")
Still not connected
```plaintext
$ ./launcher enter data
x86_64 arch detected.
root@sober-data:/# export SVWAIT=300
sv stop nginx
sv stop unicorn
sv stop postgres
exit
fail: nginx: unable to change to service directory: file does not exist
fail: unicorn: unable to change to service directory: file does not exist
ok: down: postgres: 0s, normally up
logout
```
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [February 6, 2025, 6:12am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/8 "2025-02-06T06:12:13Z")
> [@sober](#):
>
> $ ./launcher enter data
> x86\_64 arch detected.
> root@sober-data:/#
This implies you were connected to the container. (Just ensure that the `web_only` container remains stopped during the rebuild of the `data` container.)
> ok: down: postgres: 0s, normally up
This is the output that matters. It means `postgres` has now shut down cleanly and you can continue with the next steps.
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 6, 2025, 6:20am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/9 "2025-02-06T06:20:08Z")
```plaintext
./launcher enter data
x86_64 arch detected.
root@sober-data:/# sv stop postgres
ok: down: postgres: 0s, normally up
root@sober-data:/# exit
logout
root@sober:/var/discourse$ ./launcher rebuild data
x86_64 arch detected.
Ensuring launcher is up to date
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 600 data
data
2.0.20250129-0720: Pulling from docker-hub-china/discourse-base
Digest: sha256:d798a945ca4d31c29e5d263cdaf807bafab9b5f6737be0b1b852bea0063a3b91
Status: Image is up to date for registry.cn-wulanchabu.aliyuncs.com/docker-hub-china/discourse-base:2.0.20250129-0720
registry.cn-wulanchabu.aliyuncs.com/docker-hub-china/discourse-base:2.0.20250129-0720
/usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2025-02-06T06:19:20.379635 #1] INFO -- : Reading from stdin
I, [2025-02-06T06:19:20.380959 #1] INFO -- : Skipped missing before_code hook
I, [2025-02-06T06:19:20.380976 #1] INFO -- : Skipped missing before_db_migrate hook
I, [2025-02-06T06:19:20.380983 #1] INFO -- : Skipped missing after_code hook
I, [2025-02-06T06:19:20.383923 #1] INFO -- : File > /etc/service/postgres/run chmod: +x chown:
I, [2025-02-06T06:19:20.386435 #1] INFO -- : File > /etc/service/postgres/log/run chmod: +x chown:
I, [2025-02-06T06:19:20.389343 #1] INFO -- : File > /etc/runit/3.d/99-postgres chmod: +x chown:
I, [2025-02-06T06:19:20.391719 #1] INFO -- : File > /root/install_postgres chmod: +x chown:
I, [2025-02-06T06:19:20.394375 #1] INFO -- : File > /root/upgrade_postgres chmod: +x chown:
I, [2025-02-06T06:19:20.394471 #1] INFO -- : Replacing data_directory = '/var/lib/postgresql/15/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.394742 #1] INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.394972 #1] INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.395126 #1] INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.395261 #1] INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.395400 #1] INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.395510 #1] INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.395622 #1] INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.395723 #1] INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T06:19:20.395845 #1] INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres peer in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T06:19:20.395930 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T06:19:20.396007 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T06:19:20.396096 #1] INFO -- : > if [-f /root/install_postgres]; then
/root/install_postgres && rm -f /root/install_postgres
elif [-e /shared/postgres_run/.s.PGSQL.5432]; then
socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
fi
initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
```
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [February 6, 2025, 6:30am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/10 "2025-02-06T06:30:23Z")
> [@sober](#):
>
> ```plaintext
> initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
>
> ```
Is the rebuild stuck at this point? If so, cancel it and run this instead then post the results.
```plaintext
./launcher start data
./launcher enter data
psql --version
apt-get update
```
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 6, 2025, 7:04am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/11 "2025-02-06T07:04:25Z")
Thank you very much. Let me go back to the docker version and postgres.template.yml
```plaintext
./launcher rebuild data
x86_64 arch detected.
Ensuring launcher is up to date
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 600 data
data
2.0.20250129-0720: Pulling from docker-hub-china/discourse-base
Digest: sha256:d798a945ca4d31c29e5d263cdaf807bafab9b5f6737be0b1b852bea0063a3b91
Status: Image is up to date for registry.cn-wulanchabu.aliyuncs.com/docker-hub-china/discourse-base:2.0.20250129-0720
registry.cn-wulanchabu.aliyuncs.com/docker-hub-china/discourse-base:2.0.20250129-0720
/usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2025-02-06T07:02:42.768651 #1] INFO -- : Reading from stdin
I, [2025-02-06T07:02:42.769907 #1] INFO -- : Skipped missing before_code hook
I, [2025-02-06T07:02:42.769923 #1] INFO -- : Skipped missing before_db_migrate hook
I, [2025-02-06T07:02:42.769933 #1] INFO -- : Skipped missing after_code hook
I, [2025-02-06T07:02:42.772767 #1] INFO -- : File > /etc/service/postgres/run chmod: +x chown:
I, [2025-02-06T07:02:42.775230 #1] INFO -- : File > /etc/service/postgres/log/run chmod: +x chown:
I, [2025-02-06T07:02:42.777690 #1] INFO -- : File > /etc/runit/3.d/99-postgres chmod: +x chown:
I, [2025-02-06T07:02:42.779645 #1] INFO -- : File > /root/install_postgres chmod: +x chown:
I, [2025-02-06T07:02:42.781825 #1] INFO -- : File > /root/upgrade_postgres chmod: +x chown:
I, [2025-02-06T07:02:42.781974 #1] INFO -- : Replacing data_directory = '/var/lib/postgresql/15/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.782261 #1] INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.782427 #1] INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.782551 #1] INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.782661 #1] INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.782762 #1] INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.782877 #1] INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.782974 #1] INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.783076 #1] INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-06T07:02:42.783180 #1] INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres peer in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T07:02:42.783258 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T07:02:42.783334 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-06T07:02:42.783416 #1] INFO -- : > if [-f /root/install_postgres]; then
/root/install_postgres && rm -f /root/install_postgres
elif [-e /shared/postgres_run/.s.PGSQL.5432]; then
socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
fi
initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
```
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [February 6, 2025, 7:30am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/12 "2025-02-06T07:30:41Z")
> 2.0.20250129-0720: Pulling from docker-hub-china/discourse-base
Can you confirm whether your server is in China?
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 6, 2025, 10:58am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/13 "2025-02-06T10:58:57Z")
Mirror is no problem, this is the mirror China network acceleration method， otherwise the mirror has no network speed
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [February 6, 2025, 1:38pm UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/14 "2025-02-06T13:38:48Z")
I moved your queries to a new topic. I believe this is related to running the update from China.
Based on your log output, the rebuild seems to fail at `apt-get update`. I would recommend using a VPN to connect your server to the `apt` repositories.
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 6, 2025, 2:08pm UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/16 "2025-02-06T14:08:37Z")
I also do a Chinese network acceleration process for apt-get update. I would like to know which software is updated mainly for apt-get update
I’d rather know what the root cause is that /shared/postgres\_run/.s.PGSQL.5432 cannot connect
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [February 6, 2025, 2:16pm UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/17 "2025-02-06T14:16:02Z")
Are you able to reach the repository below from your server?
```plaintext
curl -v https://apt.postgresql.org/pub/repos/apt/
```
The repository is needed to [install](https://github.com/discourse/discourse_docker/blob/efd6bc8ccbd9057c04d909ff48ecf8b704cae3ff/templates/postgres.template.yml#L117-L118) the old PostgreSQL packages used during the update.
> [@sober](#):
>
> I’d rather know what the root cause is that /shared/postgres\_run/.s.PGSQL.5432 cannot connect
This is typically caused when the database was not shut down properly. We had fixed it earlier when you started and stopped the `data` container. The error is not seen in your [latest log output](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/11).
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 7, 2025, 12:56am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/18 "2025-02-07T00:56:51Z")
You mean the PostgreSQL version is too old, causing problems. This upgrade can be integrated into the Discourse/base processing in the mirror. I use the mirror’s Discourse/base: 2.0.20250129-0720.
Is there any problem with my understanding? What is the version number of the PostgreSQL that works correctly and the version number of the PostgreSQL that has issues?
Or perhaps the issue lies with the fact that the mirror I am using is too recent, causing problems with the data build. I need to construct the data using the mirror Discourse/base: 2.0.20250114-0014 to accommodate the PostgreSQL upgrade.
---
### Author:  [@sober](https://meta.discourse.org/u/sober)
#### Post date: [February 8, 2025, 2:53am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/19 "2025-02-08T02:53:50Z")
I got the upgrade PostgreSQL15
Templates need to be used in sequence
postgres.13.template.yml
postgres.15.template.yml
postgres.template.yml
postgres.13.template.yml, postgres.15.template.yml file China network acceleration configuration
```plaintext
run:
- exec: cat /etc/os-release && psql --version
- exec: |
if [-f /etc/apt/sources.list]; then
sudo sed -i 's/deb.debian.org/mirrors.ustc.edu.cn/g' /etc/apt/sources.list
else
echo "deb http://mirrors.ustc.edu.cn/debian bookworm main contrib non-free non-free-firmware" | sudo tee /etc/apt/sources.list
echo "deb http://mirrors.ustc.edu.cn/debian bookworm-updates main contrib non-free non-free-firmware" | sudo tee -a /etc/apt/sources.list
fi
- exec: |
if [-f /etc/apt/sources.list.d/debian.sources]; then
sudo sed -i 's/deb.debian.org/mirrors.ustc.edu.cn/g' /etc/apt/sources.list.d/debian.sources
else
sudo bash -c 'cat > /etc/apt/sources.list.d/debian.sources <
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [March 10, 2025, 2:54am UTC](https://meta.discourse.org/t/postgresql-update-fails-from-china/350869/20 "2025-03-10T02:54:07Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.