Skip to content

feat(postgresql): Update pgx to v5#5757

Merged
kodiakhq[bot] merged 4 commits intomainfrom
feat/pgx_v5
Dec 18, 2022
Merged

feat(postgresql): Update pgx to v5#5757
kodiakhq[bot] merged 4 commits intomainfrom
feat/pgx_v5

Conversation

@yevgenypats
Copy link
Copy Markdown
Contributor

@yevgenypats yevgenypats commented Dec 18, 2022

This is a follow-up to #5733 (see discussion there). and needed so we can incorporate this nice bit: jackc/pgx#1441

The jackc/pgx#1441 is not a pre-requirement for this to go through. even better we should prob ship this first and see that v5 works for us and for our users and if not we can do the same fix for v4 (we will just have to fork it as I don't think v4 accepts anymore contributions)

@yevgenypats yevgenypats requested review from a team, disq and erezrokah and removed request for a team and disq December 18, 2022 10:06
@yevgenypats yevgenypats changed the title Feat/pgx v5 feat(postgresql): Update pgx to v5 Dec 18, 2022
Copy link
Copy Markdown
Member

@erezrokah erezrokah left a comment

Choose a reason for hiding this comment

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

Looks good overall. Let's merge this so we can battle test is on main

}
atomic.AddUint64(&c.metrics.Errors, 1)
c.logger.Error().Err(pgErr).Str("table", pgErr.TableName).Msg("failed to execute batch with pgerror")
return fmt.Errorf("failed to execute batch with pgerror on table %s: %w", pgErr.TableName, err)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Since this stops the sync (correct me if I'm wrong), maybe add a call to action?
Try skipping this table via 'skip_tables: ["<table_name>"]' and re-running the sync command

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think no need, better we get the report and fix it asap. This is basically equivalent of panic, it shouldn't happen mostly as validation should happen in our type system.

@yevgenypats yevgenypats added the automerge Automatically merge once required checks pass label Dec 18, 2022
@kodiakhq kodiakhq bot merged commit ce2aaf5 into main Dec 18, 2022
@kodiakhq kodiakhq bot deleted the feat/pgx_v5 branch December 18, 2022 11:30
kodiakhq bot pushed a commit that referenced this pull request Dec 20, 2022
🤖 I have created a release *beep* *boop*
---


## [1.9.0](plugins-destination-postgresql-v1.8.0...plugins-destination-postgresql-v1.9.0) (2022-12-20)


### Features

* **postgresql:** Update pgx to v5 ([#5757](#5757)) ([ce2aaf5](ce2aaf5))


### Bug Fixes

* **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.2 ([#5583](#5583)) ([d721c4e](d721c4e))
* **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.3 ([#5639](#5639)) ([6452d0e](6452d0e))
* **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.4 ([#5649](#5649)) ([b4aa889](b4aa889))
* **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.5 ([#5661](#5661)) ([b354b8a](b354b8a))
* **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.6 ([#5790](#5790)) ([8e2663c](8e2663c))
* **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.7 ([#5797](#5797)) ([15da529](15da529))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Automatically merge once required checks pass

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants