Add blog post on "How to Configure FerretDB to work on Percona Distribution for PostgreSQL" #2911
Conversation
This file contains 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
|
Marketing blog posts should be reviewed by @ptrfarkas and @AlekSi. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2911 +/- ##
==========================================
- Coverage 63.62% 63.58% -0.04%
==========================================
Files 451 451
Lines 23583 23583
==========================================
- Hits 15005 14996 -9
- Misses 7610 7620 +10
+ Partials 968 967 -1 see 2 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
Fashander
changed the title
AlekSi
reviewed
Jun 26, 2023
| tags: [tutorial, postgresql tools] | ||
| --- | ||
|
|
||
|  |
There was a problem hiding this comment.
I don't think this alt text is accurate
|
|
||
| That's exactly what you get when you configure FerretDB for your Percona Distribution of PostgreSQL! | ||
|
|
||
| In this article, we'll guide you through the advantages of using FerretDB and how you can configure it to work natively on Percona Distribution of PostgreSQL and explore how FerretDB's commands appear in PostgreSQL, on Percona. |
| Many software companies have built their applications on top of the database, extended its functionality, and provided robust infrastructures and services for it. | ||
| Percona is one of those companies, and have contributed immensely to the ecosystem with their array of PostgreSQL tools, extensions, and services. | ||
|
|
||
| A core part of the PostgreSQL Distribution provided by Percona is the Percona Server for PostgreSQL which is an enhanced version of the PostgreSQL DBMS itself, containing optimized features for better query performance, storage engine, and monitoring capabilities. |
website/blog/2023-06-26-configure-ferretdb-work-percona-distribution-postgresql.md
Outdated
Show resolved
Hide resolved
website/blog/2023-06-26-configure-ferretdb-work-percona-distribution-postgresql.md
Outdated
Show resolved
Hide resolved
website/blog/2023-06-26-configure-ferretdb-work-percona-distribution-postgresql.md
Outdated
Show resolved
Hide resolved
website/blog/2023-06-26-configure-ferretdb-work-percona-distribution-postgresql.md
Outdated
Show resolved
Hide resolved
| `ferretdb` database should now be in context. | ||
| Let's proceed by setting `SET search_path TO ferretdb;` and then displaying the tables (this is akin to the collection we created earlier) in the database using `\dt`. | ||
|
|
||
| ```sql |
There was a problem hiding this comment.
| We can see two tables: one containing the metadata for the database and the other containing the `test` collection we created on Studio 3T. | ||
| Let's view the table content in PostgreSQL: | ||
|
|
||
| ```sql |
There was a problem hiding this comment.
| ferretdb=# table test_afd071e5; | ||
| ``` | ||
|
|
||
| ```sh |
There was a problem hiding this comment.
…bution-postgresql.md Co-authored-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
…bution-postgresql.md Co-authored-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
…bution-postgresql.md Co-authored-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
…bution-postgresql.md Co-authored-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
|
@AlekSi @ptrfarkas PTAL |
AlekSi
changed the title
AlekSi
reviewed
Jun 27, 2023
website/blog/2023-06-26-configure-ferretdb-work-percona-distribution-postgresql.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
That image uses a wrong product name
…bution-postgresql.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Readiness checklist
task all, and it passed.@FerretDB/core), Labels, Project and project's Sprint fields.