PostgreSQL

13 February 2025 04:07

https://chat.whatsapp.com/I3EPdf8Yik7FcJAQf8G3jz

PostgreSQL

12 February 2025 08:52

Anything between a couple of seconds and a couple of days. In link/clone mode, the complexity of the schema determines how long it takes, basically.

PostgreSQL

12 February 2025 06:45

How much downtime needed 1 tb db upgrade with pg_upgrade

PostgreSQL

10 February 2025 20:43

Check limitations https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html#CHAP_Source.PostgreSQL.Limitations

PostgreSQL

10 February 2025 17:28

Hi
Has anyone tried replicating a postgres db from VM to Rds ?
Im aware that the streaming replication won't work since it requires physical backup restore.
Is it possible in Logical Replication? If yes anyone can guide me. Thanks in advance

PostgreSQL

10 February 2025 16:00

im not doing delete.
im talking about insert into - will this lock the main_table? the table that i select from

PostgreSQL

10 February 2025 15:58

table has a fk constraint on main_table

PostgreSQL

10 February 2025 15:04

Yes, if there are constraints / foreign keys

PostgreSQL

10 February 2025 13:57

Hi
does running insert into table from main_table can somehow create a lock on main_table?

PostgreSQL

09 February 2025 13:11

It's for tiny databases with no real users where large downtime is affordable.

PostgreSQL

09 February 2025 13:09

If you're going the pg_dumpall route i would suggest to export only the schema, apply the schema, check that there are no errors, and then import the data separately

PostgreSQL

09 February 2025 13:06

Namely: a function that called a function by an extention that changed an IMMUTABLE to MUTABLE

PostgreSQL

09 February 2025 13:05

As far as I understand, using pg_dumpall for upgrading will still be more reliable

PostgreSQL

09 February 2025 13:01

That's why we do testing before running in production. Not so much issues these days on Linux.

PostgreSQL

09 February 2025 12:58

Pg upgrade with link method depends on number of tables rather than db size or number of databases. On good enough hardware it can still be very fast. Crunchy article has some stats.

https://www.crunchydata.com/blog/examining-postgres-upgrades-with-pg_upgrade

PostgreSQL

12 February 2025 22:23

Hello there, I need your help

When I’m about to finish the installation, this error shows up ( Problem running post-install step. Installation may not complete correctly
The database cluster initialisation failed. )
How can I fix this?

PostgreSQL

12 February 2025 08:50

There's no GRANT SELECT ON ALL OBJECTS IN ALL DATABASES. You'll need to generate/write an SQL command at least for each schema in each DB.

PostgreSQL

12 February 2025 06:23

Hi everyone can i know how to create a user with no superuser and he has only select privilege for all databases.

PostgreSQL

10 February 2025 17:29

Logical replication should work, provided there is access to target rds from VM. AWS DMS uses same postgres logical replication under the hood.

PostgreSQL

10 February 2025 16:51

Nope but all bets are off if it's redshift. You should ask AWS support, it's not community postgres.

PostgreSQL

10 February 2025 15:59

then during the query on table, you won't be able to delete tuples from main_table because it would render the foreign constraint invalid

PostgreSQL

10 February 2025 15:58

why exactly if there are constraints/fk it will require lock on the main_table?
waht about if it's redshift?

PostgreSQL

10 February 2025 15:02

Hello and welcome to this chat. Here we discuss PostgreSQL and provide best-effort voluntary support on Postgresql issues.
If you have any question, try asking kindly, including log files, error descriptions and perhaps what you're trying to do.

- 🚫 photos and screenshots
- 🚫 spam and offtopic
- ✅ questions with log files and clear explanation of what's gone wrong

⬇️ Press the button down here ⬇️

PostgreSQL

09 February 2025 14:34

I ran tests myself a while ago, from very small to TB range. The only measurable difference was schema complexity... I.e. how many tables in how many databases. Creating the hardlinks is essentially instant.

PostgreSQL

09 February 2025 13:09

However, sometimes you might also benefit from dropping indexes, keys and constraints and readding them later if you have a lot of interwined tables

PostgreSQL

09 February 2025 13:07

Thanks for the clarifications 🙏

PostgreSQL

09 February 2025 13:05

Migrating data-only databases i've never had any issues whatsoever
Migrating databases that also implement functions and stored procedures and materialized views using said procedures, i had issues where some things were deprecated or changed and so some functions would not be valid anymore

PostgreSQL

09 February 2025 13:03

I don't see a much trouble on this approach.
This may require a lot of attention to constraints/constraint functions/user-defined types/sequences...
Every type of that expected to be dealt with once, though.


There may be troubles at 1000 replications running in parallel. At least, I expect significant wal writing slowdowns due to 1000 decoders.
However, base-by-base approach should get rid of it.

PostgreSQL

09 February 2025 13:00

I read somewhere that pg upgrade can cause errors, although everything was updated well in my test

PostgreSQL

09 February 2025 12:57

Yeah but this one automates 100% of it, no need to ask the developers whenever they need to shuffle dbs around