Great questions, all of them. Here are the basic answers:
1. Integration between Advanced Server and BART is certainly a better match than barman. Barman is available for the community version, but is not compiled or packaged with it outside of what may be provided by an independent party or 2nd Quadrant themselves.
2. Close! PostgresRocks.net is not quite an analog for OTN in its entirety; consider it very close to the community purposing of OTN, except this platform is to enable growth of Postgres at large and is not restricted to EDB Postgres itself (or the associated tool suite). We will build out different components as the users call for it and where it makes sense, so consider this a living experiment - where need or interest arises, we have the ability to adapt to that change.
3. You certainly can post questions related to EDB Postgres if curious about certain aspects, technical or otherwise - but you can also post about Postgres and its use in its entirety, with no coupling to any formalized solution. EDB does provide specific forums on here (such as this board) for the EDB product suite, and questions / discussion are what will make it thrive! Additionally, if we see an EDB customer here who isn't quite getting the answer they need in this broader forum, we'll often take the next step and pull them into a direct engagement.
4. Have you tried the StackBuilder Plus installation (https://www.enterprisedb.com/downloads/postgres-postgresql-downloads)? Or am I misunderstanding the question?
Thanks for participating, very excited to see that you've jumped in on several new threads already!
... View more
Ah, the misunderstanding makes sense now. The lefthand column shows the features of and our support subscriptions for PostreSQL, the community version. (As an aside, we do provide PostgreSQL via an installer and RPM's, and we also support distributions made available both from EDB and the most common community sources: EnterpriseDB installers, ftp.postgresql.org, yum.postgresql.org, apt.postgresql.org, and where it's contained as a bundle from Red Hat Enterprise Linux, Fedora, Ubuntu, CentOS, Amazon Linux, SuSE or Debian from the original vendors.)
... View more
Sure can! https://www.enterprisedb.com/products/compare-postgres-databases has the high-level outline. Please let us know if there are any specific enhancements or alterations you might have in mind while making the consideration.
... View more
We're four weeks into the life of PostgresRocks.Net, and boy, do we see a lot of traffic coming across to the blogs and knowledge base - over 80,000 combined views! We're excited to have this platform out there for everyone, but we want to hear from you - so what would you like to see here? Featured topics? Contests? Event coverage? Let us know - we want the platform to be what is needed by you, the user.
... View more
I'm just getting started with PostgreSQL. Where do I start?
There are many places to start; PostgreSQL.org has a ton of mailing list threads related to this question and probably thousands of others, and Stack Overflow holds a lot of answer-oriented information as well. Here are a few good places you can start:
2. Couple of videos about architecture and administration on youtube::
3. Free online training::
3. And tons of blogs from Robert and other contributors.
Below is a basic overview that was drafted by Sachin Fate of EDB:
Architectural Overview of PostgreSQL
PostgreSQL is the world's most advanced open source database. It is built on top of many of the same RDBMS fundamentals which are the basis of all modern-day relational databases, such as Oracle, DB2, SQL Server.
A Postgres database cluster is a collection of databases which is stored at a common file system location, or data directory.
When you start the postgresql database cluster, it will start the postmaster process as well, and will allocate shared memory to the database cluster. The postmaster does not itself interact with the user and should be started as a background process. Only one postmaster should be run on server for one database cluster.
The postmaster process is one of the most important processes in postgresql. It works as a supervisor process, which means that it monitor all the processes, and whenever any process fail, it will try to restart it.
The postmaster is also work as a listener in postgresql; it accepts the connection requests from users, and validates it, then it will initiate a new process for additional new connection requests.
A shared memory area is allocated by a postgresql server during start up. This area is also divided into several fixed-size sub-areas.
1) Shared Buffer : PostgreSQL loads pages within tables and indexes from a persistent storage object to the buffer, and operates them directly.
2) WAL buffer : To ensure that no data is lost by server failures, PostgreSQL supports the write-ahead log, or WAL mechanism. WAL data (also referred to as “xlog” records) are transaction logs in PostgreSQL; the WAL buffer is a buffering area which stages the WAL data before writing to the persistent storage.
BACKGROUND PROCESSES :
BGWRITER: Also known as the background writer, the role of BGWRITER is to reduce the impact of intensive checkpoint writing. The background writer continues to flush dirty pages incrementally, with the intent of causing a minimal impact on any critical database activity. By default, the background writer wakes every 200 milliseconds (as defined by bgwriter_delay) and flushes bgwriter_lru_maxpages (the default is 100 pages) at maximum.
CHECKPOINTER : CHECKPOINTER, the checkpoint process, has two aspects: the preparation of database recovery points, and the cleaning of dirty pages on the shared buffer pool.
AUTO VACUUM : Autovacuum is a daemon within PostgreSQL which automates the execution of VACUUM and ANALYZE commands; when enabled, it calls the autovacuum worker processes – or, more precisely, requests a spawning of the processes from the PostgreSQL server.
WAL WRITER : The WAL Writer process periodically writes and flushes records within the WAL data on the WAL buffer to persistent storage.
STATASTIC COLLECTOR : In this process, statistical information, such as the attributes for pg_stat_activity or pg_stat_database, is collected.
ARCHIVER : In this process, archiving logging is executed.
LOG WRITER : This process writes error messages into log files.
... View more
Similar to other RDS offerings, there are limitations that are specific to PostgreSQL and some which are simply inherent to RDS. Specific to RDS, database upgrades are limited to versions which are supported by RDS - so availability may lag behind the community release dates. Also, OS upgrades, which are related to Amazon's Machine Image (in this case, their Linux AMI), are managed by Amazon. You're able to configure the "when" element, via the usual RDS inputs (console, API, or AWS's CLI), though the image is hardened to their Linux AMI (more on that here if necessary).
Storage-wise, instances require a minimum of 5GB, with a max of 6TB per instance. You're capped at 40 instances of PostgreSQL overall.
Connections to that storage require a *minimum* of three reserved for RDS-level actions by Amazon, so when setting the value for max_connections, you have to add those three to your overall maximum. Given that you're already in RDS, it may not be worth mentioning, but from a tablespace perspective, you can't use those parameters to increase IO efficiency (IE, splitting the IOPs, isolating tablespaces for performance requirements). Tablespaces *are* supported, but they're all housed on a single LV. Finally, altering data types (alter enum) has been around on PostgreSQL since 9.1, but isn't supported on RDS on versions lower than 9.5.6/9.6.2.
Many of the differences or contrasts are really "How do we know what is best on RDS" questions based on needs, such as using Logical Replication versus read replicas, failover requirements versus multi-zone HA, connection limitations based on memory defined for the RDS instance, etc. Some of these are dealt with here in the Amazon documentation for RDS at large.
Are there are any things in particular you're concerned with while going through the migration? Hopefully these are a decent start in getting some answers to questions you may have.
... View more
Greetings, Fellow Rockers!
In celebration of the launch of PostgresRocks.Net, EDB is has brought together our A-Team - including such names as Bruce Momjian, Robert Haas, Dave Page and Vibhor Kumar - to field an answer from the audience. Ask your Postgres questions and kudo your favorite ones! The question with the most kudos will be picked at 6pm Eastern Time tonight, and the the selected question will win a wireless speaker.
So don't be shy, ask away and we'll swing for the fences!
The EDB Team
... View more