We're honored by the recognition and are very happy that people enjoy using
@PostgreSQL
!
The
@PostgreSQL
community will continue working hard on building the world's most advanced open source relational database.
Tomorrow, the
@PostgreSQL
11 RC (Release Candidate) 1 is made available. If all goes well, PostgreSQL 11 will be made generally available on October 18.
This would not be possible without the hard work of everyone who developed, tested, and contributed to the project. Thank you!
Many applications use pagination for display purposes, and a common technique is to use "OFFSET" in your query, but are there better ways to do it?
@MarkusWinand
demonstrates some alternatives to using OFFSET:
A big part of an open source community is maintaining the project infrastructure. Today, the
@PostgreSQL
website was migrated from using Python 2 to Python 3 to ensure we can continue to support the modern requirements of the community:
Interested in running WebAssembly in
@PostgreSQL
? Try out the "wasm" PostgreSQL extension, which lets you run compiled WebAssembly programs: directly in PostgreSQL
Did you know in
@PostgreSQL
11, you can now use a "web search" style query with PostgreSQL's full text search functionality? Take a look at the new "websearch_to_tsquery" function, documented here:
`psql
@postgresql
`
psql (10.4)
Type "help" for help
@postgresql
=> SELECT thanks();
thanks
--------
We've reached 5432 followers!
Thank you for supporting our community twitter feed - we're excited to keep providing helpful content around our database and open source community.
Thanks for the recognition!
@PostgreSQL
owes its success to its dedicated community of developers, advocates, and users who help make our free and open source database software better every day!
Give
@PostgreSQL
a try:
The first release candidate for
@PostgreSQL
12 is scheduled for September 26.
The GA is tentatively scheduled for October 3.
Start catching up on all the new features that will be coming up in the latest release of PostgreSQL!
Did you know that
@PostgreSQL
lets you set the storage mode for individual columns (e.g. inline vs. TOAST, compressed vs. uncompressed)?
@pwramsey
demonstrates how modifying the storage mode on a column boosts a
@PostGIS
query's performance by 500%:
What are "materialized views" and how do they work in
@postgresql
?
@steph_baltus
wrote up a guide for how she used materialized views in her application as well as advice for using them in production:
Coming in
@PostgreSQL
12: No more "recovery.conf" file: all those settings are now set in the main configuration file. A "recovery" or "standby" instance can be initiated with a "recovery.signal" or "standby.signal" file!
See the commit here:
When you create and use an index
@postgresql
, what is the database actually doing?
@louisemeta
's presentation explains how each index works, with a crocodile there to help tell the story:
As the year winds down, why not study how
@PostgreSQL
processes a query?
@suzuki_hironobu
provides a detailed guide with several examples of how queries are handled internally in PostgreSQL:
pgloader is an open source tool that lets you load data from a variety of data sources in
@PostgreSQL
with support for parallelism. You can learn more about the project here and see if it can help you with your projects!
It's true, using COPY is really fast for data ingestion in
@postgresql
! Read how
@danielfone
turned a potential 16 hour data import into a 4 minute one:
Congratulations to the new
@postgresql
committers!
Etsuro Fujita
Peter Geoghegan
Amit Kapila
Alexander Korotkov
Thomas Munro
Michael Paquier
Tomas Vondra
Read more here:
Don't want to have your primary key to be an ordered sequence of integers that people can easily guess?
@emerson_lackey
shows how to use
@postgresql
to create random, unique integers for your PKs:
A common pitfall with
@postgresql
is to create a foreign key constraint, but forget to create an index, and then go perform a lot of lookups on that foreign key!
Cameron Ellis demonstrates how to find foreign keys that are missing indexes:
The "feature freeze" for
@postgresql
11 is in effect. The community will now be hard at work on making sure that all of the new features will meet the quality standards that
@postgresql
is known for in time for the release later this year!
How do you upgrade
@postgresql
versions for a 50 terabyte database while minimizing downtime?
Reinier Hassjes discusses his experience and the solution his team developed:
Writing fast
@postgresql
queries can feel like an art, but understanding how to use tools like EXPLAIN and indexing features can help!
@paveltiunov87
wrote up a case-study on using the above to optimize a query in a 10TB database:
The
@PostgreSQL
Project is not possible without the generous support of our sponsors. The sponsorship committee recently voted to update the list to reflect the significant ongoing contributions of these organizations to
@PostgreSQL
:
Thank you!
It's always a good idea to test your code, even when using
@postgresql
!
@gwaxgwax
demonstrates how to test
@postgresql
application code with the help of two Python libraries: pytest-pgsql and pgmock:
Partitioning, arrays, inheritance, JSON, UNION/INTERSECT/EXCEPT, custom data types, window functions, and more!
@NahidulHasan
explores
@PostgreSQL
features that are helpful for application development:
Looking for some more information on getting started with
@PostgreSQL
, some tips & tricks, or want to test your
@PostgreSQL
knowledge?
We've compiled a set of resources that range from one page guides, interactive exercises, and tutorials!
Want to write complex but easy-to-understand
@postgresql
queries?
@elmaddawg
demonstrates how to do so, highlighting features such as subqueries, filtered aggregates, and window functions!
What's better than
@PostgreSQL
11? How about PostgreSQL 11.1?
The first set of bug fixes will be made available this coming Thursday, November 8, along with bug fixes for the supported versions of PostgreSQL!
There many ways to contribute to
@PostgreSQL
!
In addition to the core database, there are many software projects that power the infrastructure and advocacy efforts of the PostgreSQL project. We've put together a list of some of these projects here:
Happy Anniversary! Today the official
@PostgreSQL
community account turns 1! A big thank you to our many wonderful followers and PostgreSQL enthusiasts for helping us to have a great year.
Making changes to your
@PostgreSQL
schema in an highly active production environment requires some additional considerations. Read how Vineet Gopal and team automated their migration process:
It's
#FeatureFriday
!
@PostgreSQL
includes support for LATERAL JOINs. Classic use-case: Need the top-N for some set?
SELECT *
FROM server set
CROSS JOIN LATERAL
(SELECT * FROM log
WHERE = log.server_id
ORDER BY log.received_at DESC LIMIT 20) as topN;
They say it is important to put comments in your code, but what about in your databases?
@abdullahalger
shows how you can add comments to your
@postgresql
tables, columns, and other database objects:
Thank you for the recognition
#OSCon
! The
@PostgreSQL
project could not achieve this without the hard work of our dedicated community that builds and advocates for the world's most advanced open source relational database!
The upcoming
@postgresql
11 release adds more support for queries using "WINDOW" functions, but what exactly was added?
@JavaOOQ
wrote up an analysis of the new features and demonstrates how they work:
You can use the LISTEN/NOTIFY in
@postgresql
to send asynchronous notifications in your applications!
@citizen428
provides an example of how to combine this feature with websockets: