avivallssa

Several times, I have seen some discussions talking about AWS outages or Azure outages or some specific cloud services being down. I now believe that people also become similarly concerned when Claude like GenAI assistants are down, especially when you have taught it all the relevant skills, and waiting for it to execute a task.

We tried Claude Code vs our migration tool: HexaRocket, for Oracle to PostgreSQL code objects conversion with varying complexities.

While HexaRocket is a commercial tool, it is interesting to point that Claude Code, as expected, was never deterministic.

Sometimes, Claude Code provides incorrect conversions that appear correct, but can be very wrong.

This extension emulates Oracle's UTL_SMTP in PostgreSQL to send emails from database.

This is to only simplify rewrites of stored procedures during Oracle to PostgreSQL migrations.

When time matters, we should pick timestamp(0) in PostgreSQL

For this reason, it is wise to implement an option to switch may be. We put that feature so that people can switch between white and dark background

There is no doubt a debate around Client-side and Server-side connection pooler. But, utilizing the Client-side connection pooling using such advanced drivers should never be taken lightly.

Understood. It is no doubt the maintenance and the time to build. However, it does take some efforts to build Oracle forms that requires a good amount of development time in PL/SQL and for customization of forms screens.

Curious to understand the reason of not choosing a modern UI and backend using Open Source tech stack such as React/Java/Golang/PostgreSQL ?

There was a discussion earlier on HN whether it is OK to steal content if its open on Web.

https://news.ycombinator.com/item?id=40833323

However, the extension to that is the Copyrights now. According to me, as long as the Idea creator is a Human, it should not matter if its AI and any LLM creating the art.

The human who gives the prompt may be the Author. This can be concerning but challenging for Legal.

PostgreSQL is definitely going to be the de-facto database for all things AI. It is a database for the future with extensive integrations, advanced extensions for semantic and hybrid search involving vectors and keywords.

Some of the upgrades techniques presented in this talk are :

1. Using pg_dumpall 2. Using pg_dump and pg_restore 3. Using pg_upgrade without hard links 4. Using pg_upgrade with hard links 5. Logical Replication between major versions

Any other Upgrade methods you would like to discuss ?

PostgreSQL with Rust is always a great combination

As long as it cannot show anger and frustration, due to "sweating", it may be an interesting behavior.

That's a great point! The idea of robots with living skin raises so many questions. Do you think this technology could actually lead to robots that are indistinguishable from humans in our lifetime? And what ethical implications should we consider as we get closer to this reality? How should laws and regulations evolve to address these advancements?

Will this make people who make indirect money through their content, less motivated from publishing their content on the Web ? This might be arguable.

May be, there should be a similar amount of openness in publishing the content used for training commercial models.

The copyright owner should have a privilege to ask for that content to be removed from training. This may also allow individual authors to gain their share with their Advanced RAG applications, that are specially focussed on the content they own and also published on the web.

While I cannot argue about a Specific approach, I could say that hallucinations can only be minimized but with a various level of measures while working with large language models.

As an example, while we were building our AI Chatbot for Ora2Pg, the main challenge was that we used OpenAI and several other models to begin with. To avoid hallucinations to the most possible extent, we went through various levels including PDR and then Knowledge Graphs and added FAQs and then used an Agentic approach to support it with as much as information as possible from all possible contexts.

As it is very challenging for anybody and everybody to build their own models trained with their data set, it is not something possible to avoid hallucination with generic purpose LLM's unless they are trained with our data sets.

The chatbot that we built to avoid hallucination as much as we can.

https://ora2pgsupport.hexacluster.ai/

The standard for DATE must be allowing it to only store DATE but not the TIME of the DAY. Oracle may have allowed TIME as well.

I would say that what SQL Server and PostgreSQL follows should be the absolute behavior in my opinion.

It indeed creates more employment !

Using boolean would be much better when it is supported. Why not ?

Just about best practices.

PLTCL is an example. Indeed PLPerl may be too.

A unique way of getting Global Associative arrays within exception blocks as well possible with Postgres

Interesting. Would try to answer in short but rather ask you go through this webinar video i have given sometime back.

https://www.percona.com/resources/webinars/enterprise-grade-...

Like some people mentioned - you could Patroni for HA. It is a template that could be configured with etcd like distributed consensus key value stores for leader election using the world famous RAFT algorithm. Could use Watchdog/Softdog for avoiding split-brain. Now, we could also do some actions before and after failover which can be scripted. Regarding HA on other pieces such as Blob store, you could use CRR using the AWS S3. You could just mount the S3 via NFS Gateway to DB servers and let the job be done in a more simpler way. Similarly, all the problems you mentioned are solved, however, anything you feel is still challenging after going through the webinar recording, please reply back here.

Interesting

This is awesome. Sounds more exciting to see greatly used PostgreSQL stuff packed together.

Yeah thats another thing. It requires everyone to be more careful these days and do not get into such scams. However, Air Canada's ban is quite interesting there.

This issue is observed during a CHECHKPOINT when a BGWriter writes dirty or modified buffers from shared buffers to Disk. So, upon recovery after crash, the changes since the last checkpoint are applied from WAL, this time. So, we are using the changes that are in a WAL (Write-ahead-log) because the changes are already gone from Disk as you rightly said. A good question in fact.

And from PostgreSQL 11, it supporting transactions within Stored Procs is killing. Earlier, Oracle to PostgreSQL required developers to re-write a lot of logic in application to make it for PostgreSQL. Now, from PG 11, it supports transactions and that made the migrations more and more easier.

In fact, not just Oracle to Postgres migrations, but any time we think of putting business logic into an Open Source Database, I think PostgreSQL is the best of the choices we have. We always think Oracle and SQL Server are the only best options we have. In fact, PostgreSQL does a great job in handling Stored Procs. One such plprofiler like tools makes more difference for developers.