PostgreSQL

21 Mar 2025 07:13

Hello, there is a code doing a transaction with a commit at the end. This commit is taking 45min to complete. At progress side, commit was active and no wait event. We figured out by debugging the code that there were triggers fired taking long time. Is there anyway to identify this case in postgres? Commit doesn't allow explain plan.

PostgreSQL

20 Mar 2025 21:25

Where can I start with learning PostgresSQL?

PostgreSQL

20 Mar 2025 16:09

Hi, I am looking for blockchain developers and interface developers, as well as beta testers, write in private messages

PostgreSQL

20 Mar 2025 13:15

Any documents ,it will be really helpful

PostgreSQL

20 Mar 2025 12:37

I think

bluth=> \d ilya
Did not find any relation named "ilya".
bluth=> 

PostgreSQL

20 Mar 2025 11:31

Not helpful. What is the exact(!) query. What is the exact relation name.

PostgreSQL

20 Mar 2025 10:46

In fact, you'd better to collect the exact info about your errors — to know at least what should be fixed.

Not your impressions, not some other's retelling of their experience — but the exact errors and the exact code leading to them.

PostgreSQL

20 Mar 2025 10:41

Thanks for all the help

PostgreSQL

20 Mar 2025 10:38

But could be created!

PostgreSQL

20 Mar 2025 10:38

My understanding is the SQL standard lets DBMSes choose to uppercase or lowercase unquoted identifiers. So it's quite possible that Oracle does the opposite of PostgreSQL. And if you are using some form to DB Link from Oracle to PostgreSQL, I doubt there is any solution other than quoting your identifiers.

PostgreSQL

20 Mar 2025 10:37

Btw,

SELECT * FROM OWNER.TABLE;

SELECT * FROM "owner"."table"

PostgreSQL

20 Mar 2025 10:33

And patroni is the worst, of course.
(Others aren't of much use, but not a much damage either).

PostgreSQL

20 Mar 2025 10:29

You sure that this is not your application?

Is the table uppercase or lowercase in the database?
And if it's lowercase and you don't quote, you can write the object name any way you want.

OwNeR.tAbLe ...

PostgreSQL

20 Mar 2025 10:24

we have support, but the response is slow.. so just checking anyone else faced this earlier

PostgreSQL

20 Mar 2025 10:21

I don't understand what case sensitive is the problem here. Maybe provide an example.
Also don't you have a support contract with EDB?

PostgreSQL

20 Mar 2025 21:48

Just about anywhere if you have internet.

PostgreSQL

20 Mar 2025 18:59

It's not only QUITE Possible, but 100% TRUE. Oracle stores everything as UPPERCASE by default, and PG as lowercase by default. Which, should not matter UNLESS you have QUOTED things.
If NONE of your queries quote things, (especially the exports), then it should work.
The problem is that any tools that generate QUOTED object names will quote them to UPPER in Oracle, and to LOWER in PG, which means those queries cannot be moved from one to the other.
the COOL part is that if there are no quotes, then:
Select * from SomeSchema.SomeTable; Works in both places without quotes assuming the names were never quoted when created.

PostgreSQL

20 Mar 2025 14:05

https://www.packtpub.com/en-gb/product/postgresql-16-administration-cookbook-9781835460580

PostgreSQL

20 Mar 2025 13:15

Can anyone share backup strategy ?
Implementation steps and scripts

PostgreSQL

20 Mar 2025 11:52

Postgres doesn't have that error message. Not even some error message, that this text could be part of.

PostgreSQL

20 Mar 2025 11:21

we are getting “relation does not exist” error in postgres..

PostgreSQL

20 Mar 2025 10:44

First of all, figure out what exactly is sent to the database. With or without quotes.

PostgreSQL

20 Mar 2025 10:41

understood guys.. i will ask the app team to change their code..

PostgreSQL

20 Mar 2025 10:38

Now whatever framework you are using might quote every qualifier, and send "SCHEMA"."TABLE" to the database. And that object, with this exact name, does not exist.

PostgreSQL

20 Mar 2025 10:37

You write:
it comes to postgres db as select * from OWNER.TABLE

This is an application problem, not a database problem.

But as long as you write SCHEMA.TABLE and not "SCHEMA"."TABLE", you are fine.

PostgreSQL

20 Mar 2025 10:35

postgres tables are in lower case.. but i am not sure, why when we trigger from oracle db, it comes as Uppercase and fails..

PostgreSQL

20 Mar 2025 10:32

Best not to use any automatic failover!

PostgreSQL

20 Mar 2025 10:29

There is no config setting in PostgreSQL that I'm aware of which alters the case handling of identifiers.

If you are mixing cases, then quoting those identifiers is what you need to do, I believe the SQL standard defines this.

Maybe EPAS has options given there Oracle compat features, but I would not be surprised if they did not.

TBH string replace on schema.identifier to quote them, does not seem a huge problem. Just get on and fix the code IMHO.

PostgreSQL

20 Mar 2025 10:23

when we query something like select *from owner.table, it comes to postgres db as select * from OWNER.TABLE.. so our query fails.. if we use select * from “owner”.”table”, it gets success

PostgreSQL

20 Mar 2025 10:19

is there any easy way that our oracle db can access postgres data without changing the existing code??