[10.x] Fix forced use of write DB connection #48015
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
I'm curious - could we just always use |
oleksiikhr
force-pushed
the
fix-force-write-db-connection
branch
from
2ecb087 to
78e7771
Compare
tpetry
added a commit
to tpetry/laravel-postgresql-enhanced
that referenced
this pull request
Sep 4, 2025
jschultz1027
added a commit
to jschultz1027/laravel_postgresql
that referenced
this pull request
Sep 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am using Read & Write Connection (with a few tricks) and Laravel Octane.
My site is read-heavy, very few where I need to use write connection to work with DB. So most endpoints only require read DB connection.
Also, I started using a new feature from laravel 10.x, it's
toRawSql, to simplify key creation for caching queries. As it turns out, queries that only require a read-only connection now also require a write connection to the database.And at possible unavailability of write database, my site goes down, although it is quite enough only read-connection for processing current requests.