2806
English speaking PostgreSQL public chat. This group is for discussions on PostgreSQL-related topics and strives to provide best-effort support as well.
... or the better Oracle compatibility. Many if not most don't realize they replace a proprietary product with another one 🤷
Читать полностью…
Hello Everyone,
I need some information on the scenarios where a company might prefer using EDB PostgreSQL over the open source version of PostgreSQL.
What factors or requirements typically lead companies to choose EDB PostgreSQL?
What advantages does EDB PostgreSQL offer compared to the open source version?
If there are any blogs or articles covering this topic, please share me.
Can any one comment which one is better for an enterprise application which has more than 1000 tables and 8000 stored procedures .
Ms SQL server or postgres
1. Which one to use
2. Why
It is going to be a saas based product, it is an ERP solution for industry
Maybe we should add a rule "if you're involved in crypto or blockchain stuff, dump your s**t somewhere else"? 🤔
Читать полностью…
We just set up a group dedicated to PG freelancers/small businesses in Europe. Topics will (probably) be jobs, rates, experiences w/ clients, improving visibility etc. pp.
Since I don't nearly know all of you out there, join us if you're interested:
/channel/+GUaaD3HwQ98zNGYy
Compared to cloud anything bare metal is already affordable. Check https://autobase.tech/
Читать полностью…
So it is timescale? My opinion is that storage is cheap and total size required depends on retention policy + Wal generated. So I don't get the problem statement here without numbers.
Читать полностью…
I guess, since I don't have like a lot of updates in the hypertable, and only it does append new data ingestion, so I can tell by logic that no need for autovacuuming, as there won't be like a lot of dead rows there in the hypertable.
and only depends on the policy set on both the hypertable and mvs refresh policy to handle this instead of autovacuum.... as I believe bt enabling autovacuum it could further complicate the problem as by default timescale has a lot of triggers like jobs, hypertable_chunks, etc... to be run when new data inserted, so I see no valid point here to enable it so far
Should it also be set for longer time to autovacuum longer than my refresh policy of my mvs?
Читать полностью…
So, we might have this situation here:
* you ingest data into your main table -> WAL gets written
* autovavuum doesn't bother looking at it yet, afterall only a tiny fraction of the table has been added
* as you left checkpoint_timeout at the default of 5 minutes, a CHECKPOINT is triggered
* you refresh your MV -> main table gets read
* main table gets visibility bits etc. refreshed, triggering a full page write, as there was a CHECKPOINT before
I can imagine that raising checkpoint_timeout to something significantly larger than your MV refresh rate will reduce your WAL count quite a bit.
That said, if your DB is in the TB range and you ingest a lot of new data, it's not a miracle that your WAL count is high too 🤷
I'm also not sure if matvievs are WAL logged. My guess would be yes. Maybe a smart(er) approach to that part would help too 🤔
Читать полностью…
And what do you believe you'll achieve with it? A WAL segment is 16MB. It doesn't grow larger if you set archive_timeout, it will just force an archiving if you didn't fill the 16MB in 500 seconds.
Raise checkpoint_timeout. Activate wal_compression if you didn't do so yet. That will probably reduce your WAL throughput.
Oh, sorry I mean 500 it is by default in second, it is approximately 8 mins
Читать полностью…
If a company lacks technical experties and does not have access to desired talent then it would make sense. I have seen a management which was scared of moving out of Oracle Support's "imaginary" safety net and needed something with "Enterprise" tag prefer EDB Postgres over Postgres. There maybe few who are using it for some special features that EDB offers such as Bidirectional replication and EDB distributed.
Читать полностью…
Hi
Can anyone suggest good sight for learning "pg_auto_failover" extension??
Better rule, blockchain is just a slow and expensive database. Don't come here unless you can reach 100Million tps at half of the postgres cost.
Читать полностью…
🔗 We are looking for a developer (blockchain)
About the company:
Decentralized platform
Responsibilities:
Development and implementation of blockchain solutions for specific tasks.
Creation and testing of smart contracts.
Support and optimization of existing blockchain systems.
Ensuring the security of blockchain applications.
Requirements:
Experience developing on solidity rust (from 2 years):
Experience creating and testing smart contracts, including decentralized applications (dapps).
Knowledge of the defi, nft, and other blockchain-based applications protocols.
Ability to work with web3. js, ethers. js or other libraries for interaction with ethereum.
experience with truffle, hardhat or similar frameworks for developing, testing and deploying smart contracts.
experience with any of the frames (vue, react, svelte)
conditions:
remote work
work in sprints
performance bonuses
salary - $5000-25000 (payment in usdt) (depending on development experience, negotiated separately)
write me a DM, I may not respond right away
Purchase price (in $$$) is only a small part of the costs of a server...
So, "the best" are probably servers from the vendor that is already in your infrastructure, by means of "we have a pipeline for the firmware patches in place, we know the out-of-band-interfaces, we stock replacement disks on site" etc.
In general, aim for the second highest CPU in the range, and go for high single core speed. Your money is *usually* spent better for RAM and I/O.
But anyway, did you really think that 1000 connections and write-anywhere part through? Because otherwise you'll probably be disappointed badly that your expensive server are idling while waiting on the DLM most of the time...
Hey everyone,
Any recommendations on-premise bare-metal servers with SSD storage. Something affordable but high-quality. 😀
We’re setting up new clusters with a multi-master configuration, aiming to handle around 1K concurrent connections. data growth about <= 3 GB / days.
Any suggestions?
Hard to tell. I'm not really familiar with Timescale. One or the other will trigger a visibility bit update, *that* should happen before the checkpoint.
Читать полностью…
Should I also have autovacuum on that hypertable for sure?
Читать полностью…
They are not a big deal, they are just having 4 or 5 column selection, along with counting column
Читать полностью…
yep, it does logged, because it does affect the hypertable.
The core problem here, is that also my refresh policy of my continous aggregation materialized views when it runs, it also affecting the wal, and I used multiple mvs build on top of each other to further divide the data in hourly, weekly, monthly, yearly, etc...
so my refresh policy has to run in a very frequent short time in order to fetch new data from the hypertable.
Also, I cannot have like a short retention period on my hypertable, because I needed these amount of data to measure our metrics like I said in even years, and for long period of time...
You could also switch to larger WAL segment size if it's just the number that worries you 😏
Читать полностью…