SkillsAdd

github/awesome-copilot · Official

migrating-oracle-to-postgres-stored-procedures

Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL.

All-time #6553 First seen Mar 11, 2026
8-week activity · all time api

Installation

$ npx skills add github/awesome-copilot --skill migrating-oracle-to-postgres-stored-procedures
View on skills.sh ↗ GitHub repository ↗

Summary

  • Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL.
  • Translates Oracle-specific syntax, preserves method signatures and type-anchored parameters, leverages orafce where appropriate, and applies explicit collation mapping (`COLLATE "C"` only when appropriate, locale collations when required).
  • Use when converting Oracle stored procedures or functions to PostgreSQL equivalents during a database migration.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-database-setup Shared topics
prisma/skills

Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, Mon…

269.8K installs
prisma-postgres Shared topics
prisma/skills

Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, an…

263K installs
prisma-driver-adapter-implementation Shared topics
prisma/skills

Required reference for Prisma ORM 7 SQL driver adapter work.

258.3K installs
prisma-upgrade-v7 Shared topics
prisma/skills

Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes.

258.1K installs
prisma-compute Shared topics
prisma/skills

Prisma Compute deployment and hosting guide. Use whenever the user mentions Prisma Compute, `pr…

253.4K installs

Also in this package

Other skills from github/awesome-copilot · top by installs.

npx skills add github/awesome-copilot
git-commit 44.5K excalidraw-diagram-generator 29.1K documentation-writer 26.2K multi-stage-dockerfile 23.4K prd 22.9K gh-cli 21.9K refactor 21.6K java-springboot 19.9K create-readme 18.1K playwright-generate-test 18K

Browse all from github/awesome-copilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38.8K
License LICENSE
Default branch main
Open issues 21
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,151 B
  • docs SUMMARY.md 471 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,841 installs

SKILL.md

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., PARAMNAME IN tablename.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.
  • Apply collation intentionally when ordering text:

- Use COLLATE "C" only when Oracle-compatible binary ordering is required and no other sort order is specified. - If Oracle used explicit linguistic sorting (for example NLSSORT = French), map to an explicit PostgreSQL locale collation instead of "C". - Use SELECT collname, collprovider, collcollate, collctype FROM pgcollation ORDER BY collname; to discover collations in the target environment.

  • Treat UNION ALL as a review checkpoint. Validate plan quality per branch and restructure if combined-branch planning causes regressions (for example, unexpected sequential scans on large tables).
  • Leverage the orafce extension when it improves clarity or fidelity.

Consult the PostgreSQL table/view definitions at .github/oracle-to-postgres-migration/DDL/Postgres/{ProjectName}/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/{ProjectName}/Procedures and Functions/{PACKAGENAMEIF_APPLICABLE}/. One procedure per file.

{ProjectName} is the project's assembly/folder name with spaces normalized to - (e.g. MyApp.DataAccess). This matches the path used by the agent and other migration skills.