Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(outputs.postgresql): add Postgresql output #11672

Merged
merged 3 commits into from
Aug 25, 2022

Conversation

powersj
Copy link
Contributor

@powersj powersj commented Aug 12, 2022

Functionally, this is the same as #8651. The differences are two fold
right now:

  1. tests all use test-containers and right now do not have the ability
    to use a local postgresql database
  2. The tests expecting pguint extension will skip untill the
    test-container startup installs that extension.

closes: #3428
closes: #3408

@telegraf-tiger telegraf-tiger bot added area/postgresql feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin plugin/output 1. Request for new output plugins 2. Issues/PRs that are related to out plugins labels Aug 12, 2022
@powersj powersj force-pushed the feat/output/postgresql branch from 81da34e to a149806 Compare August 17, 2022 16:17
@powersj powersj mentioned this pull request Aug 17, 2022
3 tasks
@powersj powersj marked this pull request as ready for review August 17, 2022 16:38
@powersj powersj added the ready for final review This pull request has been reviewed and/or tested by multiple users and is ready for a final review. label Aug 19, 2022
@reimda reimda self-requested a review August 22, 2022 19:03
Copy link
Contributor

@reimda reimda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than the all.go issue this looks good to me

@@ -1 +1,62 @@
package all

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is restoring all the output plugin imports. The PR also adds a separate postgresql.go import file here so I think we can get rid of this and it will continue to be imported.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah good catch, fixed

Functionally, this is the same as influxdata#8651. The differences are two fold
right now:

1) tests all use test-containers and right now do not have the ability
   to use a local postgresql database
2) The tests expecting pguint extension will skip untill the
   testcontainer startup installs that extension.
@powersj powersj force-pushed the feat/output/postgresql branch from a6c0626 to f1307d1 Compare August 25, 2022 13:11
@telegraf-tiger
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/postgresql feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin plugin/output 1. Request for new output plugins 2. Issues/PRs that are related to out plugins ready for final review This pull request has been reviewed and/or tested by multiple users and is ready for a final review.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Postgresql output plugin (for using with timescaledb)
3 participants