PostgreSQL

16 Oct 2024 22:33

Searching for "backup schema postgresql" pulls up the exact command needed to do it in my favorite search engine, along with a description from some stackexchange website

PostgreSQL

16 Oct 2024 22:32

RPO/RTO may be just fine. There arw different cases...


But pg_dump requires a lot of knowledge to make a reliable backup. No DDL at time of a backup, no gigabyte rows, some mess with functions order and some care about recursive foreign keys to name a few troubles...

This could be called exceptional knowledge today for non-DBA. So my answer is: you can make a usable backup system out of pg_dump, but it's a non-trivial work, usually impossible in typical environment.

PostgreSQL

16 Oct 2024 22:28

Also, pretending like you don't know what someone wants when they say they're looking for a way to back up one schema is pretty unhelpful, IMHO. You know they're looking for pg_dump -n right? So like if you want to also tell them to maybe look into other options, cool, but I mean, telling them that there's no way to do it because you hate pg_dump is just being confusing oon purpose.

PostgreSQL

16 Oct 2024 22:26

Well, pg_dump is a tool for dumping data, pg_**basebackup** is the tool for creating a proper backup

PostgreSQL

16 Oct 2024 22:24

Well, the blog post hardly recommends pg_dump. And these reasons are mentioned. But my main point is that saying "don't use pg_dump because the RPO/RTO suck" is a perfectly fine argument, but saying "pg_dump is not a backup tool" is 100% useless because it doesn't help anybody understand anything.

PostgreSQL

16 Oct 2024 22:19

Especially considering the fact that pg_dump is NOT an exact copy of the data, so the chance of your recovery failing can be high with schemas that are "messy"

PostgreSQL

16 Oct 2024 22:16

I have an exact opposite article in my drafts

PostgreSQL

16 Oct 2024 10:02

Thanks for your help

PostgreSQL

16 Oct 2024 09:54

No, it needs to be done specifically for postgresql?(I tested the code in python, it works fine)
Anyway, thanks for the reply, I will read more about it

PostgreSQL

16 Oct 2024 09:32

Hi everyone
Has anyone had a problem with sending rest request to internal url? I tried pqsl_http, PLPYTHON3U. Requests are sent (for example to google.com), but not to the url inside the local network.

PostgreSQL

16 Oct 2024 09:08

Try to fetch it with curl, then install it directly with rpm

PostgreSQL

15 Oct 2024 17:51

Thank you makes a lot of sense

PostgreSQL

15 Oct 2024 16:43

pg_dump -n schemaname

PostgreSQL

15 Oct 2024 16:35

Can anybody send me the command to take the backup of one schema with data?

PostgreSQL

15 Oct 2024 16:05

so I guess it is the best one to use here in this use case

PostgreSQL

16 Oct 2024 22:32

OP could search online in a couple of seconds and get an answer. Posing the question that way means you just don't care and I'd say a response like that is correct to perhaps further stimulate OP to research themselves

PostgreSQL

16 Oct 2024 22:30

I bet a lot of people would disagree with that too, in the sense that most people shouldn't be running that themselves rather than via a tool. But what I think is that it's silly to argue about what it means to be a backup tool. What's important is to educate people about what to do and why to do it like that. Getting stuck on the words we use to describe things isn't the way forward, in my opinion.

PostgreSQL

16 Oct 2024 22:26

Perhaps we should say "pg_dump is not a backup tool, pg_basebackup is" :)

PostgreSQL

16 Oct 2024 22:25

Very few problems are solved by getting mad at people for having bad opinions.

PostgreSQL

16 Oct 2024 22:20

I'm proud that I provoked that!

(But i'm upset a little, though, that it was unintentional).

PostgreSQL

16 Oct 2024 22:17

Main point is: pg_dump(all) has horrible RPO/RTO, and when disaster strikes and you need to get back up quickly, needing to setup and dump back in loads of data can make the difference

PostgreSQL

16 Oct 2024 22:09

I just stumbled over https://rhaas.blogspot.com/2024/10/is-pgdump-backup-tool.html

LOL Robert , *that* was quick 👏

PostgreSQL

16 Oct 2024 09:58

Check for $http_proxy and $https_proxy in your Python testbed.

PostgreSQL

16 Oct 2024 09:50

That sounds like a problem with your internal network. Did you set a proxy environment variable or so?

PostgreSQL

16 Oct 2024 09:22

Reported S H [7505889847] to admins.​​​

PostgreSQL

16 Oct 2024 08:34

Hello everyone , need help while instalation , i am trying to install postgresql14 on my rhel 7 using yum , i have followed the instructions from postgre but still i have a issue as below

[root@localhost ~]# sudo yum install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpmLoaded plugins: langpacks, product-id, search-disabled-repos
Cannot open: https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm. Skipping.Error: Nothing to do

i have disabled firewall not sure what i am missing can someone please help me here

PostgreSQL

15 Oct 2024 17:09

1) You cannot do anything good with clusters (currently).

The commodity hardware cluster are always slower than single node of the same price.
Well, it's possible to get performance gain from clusters on a low-end hardware — if you'll separate them completely. No dependencies, no links, no synchronization, and client decides where to go.
But if you didn't do that yet — perhaps, something in busyness logic prevents it, isn't it?

So, just stick to a single server. It would be faster upto a really big servers, with many hundreds of cores, tens terabytes of RAM, tens of millions IOPS.

1.5) Proxmox isn't a bare metal. Either you have a bare metal w/o proxmox, or proxmox with containers or vms.


2) All of the tasks in postgres are done by queries.
So, in order to change something — you probably would need to change queries. Or at least look at them.
In particular, if you want more performance — go and measure your queries, than start thinking about optimising them.
No silver bullet.
Just get to work and do that — measure, look at explain, change algorithms, change structures.

PostgreSQL

15 Oct 2024 16:43

$ pg_dump -h <hostname> -U <username> -W <db_name> > dumped.sql

PostgreSQL

15 Oct 2024 16:10

interesting, I'll go to check it out better.

Thank you @unfoxo and @Musty_10

PostgreSQL

15 Oct 2024 16:04

and also a connection pooler at the same time