Home/AI Data Management & Analysis/migrating-oracle-to-postgres-stored-procedures
M

migrating-oracle-to-postgres-stored-procedures

by @githubv
4.3(34)

Migrate stored procedures from Oracle to PostgreSQL, ensuring smooth transition and compatibility of business logic.

database-migrationstored-proceduresoracle-to-postgresqlbackend-developmentGitHub
Installation
npx skills add https://github.com/github/awesome-copilot --skill migrating-oracle-to-postgres-stored-procedures
compare_arrows

Before / After Comparison

1 组
Before

Migrating Oracle stored procedures to PostgreSQL is complex, error-prone, and time-consuming.

After

Guides stored procedure migration, ensuring functional consistency and reducing migration risks.

SKILL.md

migrating-oracle-to-postgres-stored-procedures

Migrating Stored Procedures from Oracle to PostgreSQL

Translate Oracle PL/SQL stored procedures and functions to PostgreSQL PL/pgSQL equivalents.

Workflow

Progress:
- [ ] Step 1: Read the Oracle source procedure
- [ ] Step 2: Translate to PostgreSQL PL/pgSQL
- [ ] Step 3: Write the migrated procedure to Postgres output directory

Step 1: Read the Oracle source procedure

Read the Oracle stored procedure from .github/oracle-to-postgres-migration/DDL/Oracle/Procedures and Functions/. Consult the Oracle table/view definitions at .github/oracle-to-postgres-migration/DDL/Oracle/Tables and Views/ for type resolution.

Step 2: Translate to PostgreSQL PL/pgSQL

Apply these translation rules:

  • Translate all Oracle-specific syntax to PostgreSQL equivalents.

  • Preserve original functionality and control flow logic.

  • Keep type-anchored input parameters (e.g., PARAM_NAME IN table_name.column_name%TYPE).

  • Use explicit types (NUMERIC, VARCHAR, INTEGER) for output parameters passed to other procedures — do not type-anchor these.

  • Do not alter method signatures.

  • Do not prefix object names with schema names unless already present in the Oracle source.

  • Leave exception handling and rollback logic unchanged.

  • Do not generate COMMENT or GRANT statements.

  • Use COLLATE "C" when ordering by text fields for Oracle-compatible sorting.

  • Leverage the orafce extension when it improves clarity or fidelity.

Consult the PostgreSQL table/view definitions at .github/oracle-to-postgres-migration/DDL/Postgres/Tables and Views/ for target schema details.

Step 3: Write the migrated procedure to Postgres output directory

Place each migrated procedure in its own file under .github/oracle-to-postgres-migration/DDL/Postgres/Procedures and Functions/{PACKAGE_NAME_IF_APPLICABLE}/. One procedure per file. Weekly Installs234Repositorygithub/awesome-copilotGitHub Stars25.7KFirst Seen7 days agoSecurity AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled ongemini-cli202codex201opencode194cursor193kimi-cli191github-copilot191

User Reviews (0)

Write a Review

Effect
Usability
Docs
Compatibility

No reviews yet

Statistics

Installs1.8K
Rating4.3 / 5.0
Version
Updated2026年10月7日
Comparisons1

User Rating

4.3(34)
5
41%
4
47%
3
12%
2
0%
1
0%

Rate this Skill

0.0

Compatible Platforms

🔧Claude Code

Timeline

Created2026年3月18日
Last Updated2026年10月7日
🎁 Agent Knowledge Cards
Survey