change of tenant for multi tenancy using pgxpool
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 14.3k
- Forks
- 1.1k
- Avg merge
- 6d 9h
- Merged PRs (30d)
- 11
Description
Hi @jackc , previous discussions had conveyed in wrong way in the issue https://github.com/jackc/pgx/issues/2007.
As per the suggestions given in previous chat. I had tried by setting up DefaultQueryExecMode to QueryExecModeSimpleProtocol. which results in creating a new connection every time and does not releases the connections after executing query.
I had removed the immutable from procedures. Everything is working as expected.
But only query is when procedures are immutable, the results of pgx are not matched with results using jdbc. May I know the reason?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the prior discussion in issue 2007 and reproduce the pgxpool behavior described with DefaultQueryExecMode set to QueryExecModeSimpleProtocol. Compare results from immutable procedures in pgx and JDBC; the issue is resolved when the discrepancy and its cause are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100