[exporter/postgres]: Exporter to OTEL data in Postgres

[destrex271]

Description:
Initial Draft PR for a Postgres Exporter, will update it with the folder structure soon

Link to tracking Issue:

• [exporter/postgres]: Exporter to save OTEL data in postgresql #35451

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: destrex271 / name: Akshat Jaimini (2ab03eb, 1183327, 7fe9727, a3b2930, cc5ff81, 7b2d133, 3b6e435, eb92ea6, 845bf41, 37ca957, 688a586, bc2c198, b08f6fc, 9384689, 6744672, d9da893, 154bbb4, 4506b16, e2f50c6, 500083a)

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[atoulme]

headers

[destrex271]

Okk, will do that.

[atoulme]

You need a metadata.yaml file and generate the README and most from there. Your initial stage should be in development, not alpha. Your initial PR should have the skeleton of the component, logic is added afterwards.

But most important, please secure a sponsor first.

[philippemnoel]

You need a metadata.yaml file and generate the README and most from there. Your initial stage should be in development, not alpha. Your initial PR should have the skeleton of the component, logic is added afterwards.

But most important, please secure a sponsor first.

What does securing a sponsor entail? I'm the CEO of ParadeDB (paradedb.com). We're happy to push for this feature, Akshat is one of our contributors and has been putting this PR as part of his contributions to @paradedb).

[destrex271]

I think this branch has become a huge mess. I think its better to raise a separate PR with all the steps followed properly this time. Apologies for any inconvenience caused.