PostgreSQL

07 October 2024 13:45

Though we have many reasons to love it, anything specific that attracts you the most ? 😊

PostgreSQL

07 October 2024 10:03

A good start would be a pg_buffercache standard extension and (a lot of) query plan analysyses with buffers, timing, wal options.

PostgreSQL

07 October 2024 09:33

How to check the cache size of tables in postgres database

PostgreSQL

06 October 2024 19:10

Pretty much.

I often find cloud solutions tend to be designed for general usecases.

Where as with your own, you have access to a lot more options to tailor your solution.

PostgreSQL

06 October 2024 18:56

Fast, Right, or Cheap. Choose 2!

PostgreSQL

06 October 2024 17:34

It's not huge...it is in the permissible limits

PostgreSQL

06 October 2024 17:33

At a very hefty price, yes

PostgreSQL

06 October 2024 17:32

You're not an engineer at all.

(I've seen a lot of people like you).

PostgreSQL

06 October 2024 17:15

Yes correct. Migrating a database to the cloud can resolve many issues, such as performance bottlenecks, scalability limitations, and infrastructure maintenance concerns. Cloud databases often offer built-in redundancy, automated backups, and enhanced security features, which can further improve reliability and uptime.

PostgreSQL

06 October 2024 17:09

Each has their own perspective..but that shouldn't be commented..

PostgreSQL

06 October 2024 17:03

While I'm all sound with my on prem which is easily scalable, less expensive and I have control over it

PostgreSQL

06 October 2024 17:02

As in a fraction of seconds we can obtain either horizontal or vertical scaling..

PostgreSQL

06 October 2024 16:59

How do you think we've done network scalability until now?

PostgreSQL

06 October 2024 16:49

Just with this u can't blame..even though I am an experienced Dba ..I am not a half-knowledger person to post the info here.. without Knowing about it...

PostgreSQL

06 October 2024 11:58

1. Mobile App Developer Internship
https://rb.gy/9ajw2d

2. Product Management Internship
https://shorturl.at/15rIM

3. Backend Developer Internship
https://rb.gy/4ngfk5

4. Technical Operations Internship
https://shorturl.at/Nn8Ie

5. Frontend Developer Internship
https://shorturl.at/1Gf9Q

6. Fullstack Developer Internship
https://rb.gy/e052g9

7. QA Engineer Internship
https://rb.gy/0g6sfy

PostgreSQL

07 October 2024 13:28

Upgraded to 17 today, already in love with it as always, happy upgrading everybody :)

PostgreSQL

07 October 2024 09:52

Do you mean buffer cache?

PostgreSQL

06 October 2024 22:28

Anybody has patroni related video

PostgreSQL

06 October 2024 19:01

t.me/catsgang_bot/join?startapp=jeHAWePvwt4yLgr3JPBhf
Meow, lets see who is OG 😼

PostgreSQL

06 October 2024 17:42

In my experience the cloud can cause just as many issues.

The cloud is not magic, it's just somebody else's computer, that you're renting.

Which comes with it's own sets of limitations and tradeoffs.

Engineering is about finding a solution which balances those tradeoffs within your constraints.

PostgreSQL

06 October 2024 17:33

Hope u r not so..if ur not emerging as per the technology..

PostgreSQL

06 October 2024 17:32

Who r u to state about me...

PostgreSQL

06 October 2024 17:16

I totally agree 💯..

PostgreSQL

06 October 2024 17:10

I have multi loud, that was just an example

PostgreSQL

06 October 2024 17:08

U can't compare one cloud provider with others as I have been using Amazon for the past 3 Years and I don't have issues with it.and moreover i need to pay money for the space which i have utilized instead i need not to buy space for future use..

PostgreSQL

06 October 2024 17:03

I have experience horrible issues with Oracle cloud

PostgreSQL

06 October 2024 17:01

Till now we have faced many issues.. atleast by using cloud we are safe ..

PostgreSQL

06 October 2024 16:54

Buying the server and maintaining it doesn't mean we did cost optimization..we need to consider other factors like.. network,scalability options in future , Performance and moreover deploying the team for doing all these activities..

PostgreSQL

06 October 2024 13:53

I am working with a table that stores SQL queries, and I need to classify them based on whether they are intended for data extraction or data modification. Specifically, I need to:
Mark queries as "Extract" if:

They are standalone SELECT queries used to retrieve data.
They are part of a WITH ... SELECT Common Table Expression (CTE).
They are COPY statements.

Mark queries as "non-extract" if:
The SELECT is combined with data modification operations like INSERT INTO, UPDATE, or DELETE.
The query involves aggregations like COUNT etc.
Additionally, I need to avoid false positives when keywords like insert, count, or delete appear in table or column names (e.g., insertbase, countless).How can I write a SQL query to correctly classify these queries in PostgreSQL?

PostgreSQL

06 October 2024 09:11

And remember that postgresql ages well, aka with new versions optimizations are introduced and performance increases