Upgrade version of Postgres - database

I wanted to ask if I understand correctly the upgrade of Postgres. Currently version 9.6 is installed on the server. I plan to raise version 12. Is the easiest solution to do a dumpall (because there are several databases on this server and I do not want to do only the whole separately) then remove the old version of postgres and install a newer one? I wanted to make sure because I found some examples. Should I still do something about this flow? I am asking for guidance.

Best is to install the old and the new version of PostgreSQL side by side.
Then you can either use pg_dumpall (from the newer version!) and psql to dump and restore, or you can use pg_upgrade.
The documentation covers that in detail.

Related

Installing Teradata in Debian or CentOS

Does anyone knows how to install Teradata in Debian or CentOS?
I wanted to give Teradata a try but I can't really find a download installer and/or clear instructions anywhere to install it.
If Plan A doesn't work (it's not simple, or even possible to install it) I was wondering if any of the following alternatives would work (and are really useful for basic usage):
Plan B: I saw a downloadable VMWare image somewhere that I could try to use.
Plan C: I think I saw an AWS (Amazon Web Services) offer time ago.
If you had done it can you point me to the right path? Otherwise, if you have tried any of the alternatives, did it work well?
Note: This is not for a production installation, but more as a learning experience, and to study this database.
Teradata runs on Suse SLES 11 only. The easiest (and recommended) way to get it on any other OS is to use the virtual edition on VMWare (Player):
Teradata Express
You need to register to be able to download.

Why shouldn't PostGIS be installed in the PostgreSQL database "postgres"?

The PostGIS installation documentation reads:
PostGIS is an optional extension that must be enabled in each database you want to use it in before you can use it. Installing the software is just the first step. DO NOT INSTALL it in the database called postgres.
We're running PostgreSQL in Docker and only need one database, so we've been using the default database, postgres. My first inclination was to install PostGIS there, but the documentation seems pretty clear that we shouldn't be doing that.
Is there a reason for PostGIS not to be installed on the default database, or is this note meant to deter people from accidentally installing PostGIS in the postgres database when their data is in the foobar database?
Thanks!
There is no danger in installing PostGIS into the postgres database. The note is just so users don't confuse themselves, as you suspected.

PostgreSQL moving database with functions

I have strange problem.
I tried to move database from one server to another using pgAdmin III.
Database was created on server with PostgreSQL 8.4.9 and I wanted to move it on second server with PostgreSQL 8.2.11.
To do It, I used "backup" option and saved file, after that I used "restore" option on new database. Tables are loaded but there aren't any functions in new database.
Maybe it is because of different postgreSQL versions?
Does anyone know the reason? Any solution?
If the functions aren't around, double-check that plpgsql is available as a language. It's available by default nowadays, but making it available used to require a create language statement.
That said, I'd echo the comments: you really should be upgrading to a 9.x Postgres version that is still supported, rather than downgrading from an unsupported version to one that is even older.
I'd recommend to do it via pg_dump from an interactive session and export the complete database to one ore more sql files. There you can use the -s switch to have only the schema which should include created functions. Having this SQL file, you can also easier backport your changes or debug if something not applying to the old fallow.

MariaDB on Windows - getting started help?

I'm trying to learn MariaDB (v5.2.4), but I'm running into some issues.
I can download and install it, but it doesn't seem to be running or I'm missing something.
I'm looking for a good resource for the 1st timer running on Windows.
A few specific questions:
Does it require MySQL to run? Alot of the installation help out there seems to be geared around upgrading from MySQL, but I want to start fresh.
Is there a management tool for the database (like SQL Server Management Studio)? If not, what do people typically use?
You do not need MySQL to run MariaDB. Once you've installed MariaDB you should be able to type
net start mysql
at a command prompt and that will start MariaDB (yes you actually type mysql)
To answer the second part of your question, I know a company called Navicat used to offer an administrative gui, but I can't seem to find it on their site anymore.
If You need GUI server tool you can use Mysqlcc (it maybe work for MariaDB) or HeidiSQL (it is trully work for me) , go to google for get it...for HeidiSQL there is a portable version as I ussualy use it..but I use it in XP.....
Here you have a post about how to install MariaDB. It's in spanish, because I haven't had time yet to translate to english.
http://www.manejandodatos.es/2013/9/probando-mariadb
For the second question, I use heidiSQL.
I have used SQLyog as a GUI for MariaDB. The free version can be downloaded from here: https://code.google.com/p/sqlyog/wiki/Downloads . Also Navicat has a Mariadb Version which is paid.
As Google code has seen a shutdown,the latest version of SQLyog Community can be downloaded from here >> https://github.com/webyog/sqlyog-community/wiki/Downloads .

Anybody using SQL Server Spatial in a production environment?

I'm looking for some spatial database features but can't upgrade to SQL Server 2008 at the moment. I've come across this open source mssqlspatial package which would provide most of the features I need however I'm hesitant to deploy it without knowing if it's production ready. I was wondering if anybody out there had deployed this package.
Thanks
Never heard of mssqlspatial, sorry. Have you considered PostGIS though? That'll give you an open source spatial database, and I believe it's quite well regarded. Never used it myself.
This isn't answer...just some additional info.
We just went to SQL Server 2008, but PostGIS would have been my first choice (wasn't my choice). As MarkJ says, it is well regarded.
You might want to checkout SharpmapV2. It's not a spatial database but you've got providers on just about everything including MsSqlSpatial:
http://sharpmapv2.googlecode.com/svn/trunk/SharpMap.Data.Providers/
And I'm seeing the same developers in both repositories (John Diss looks like a busy guy), so I think SharpMapv2 is more current:
http://mssqlspatial.codeplex.com/SourceControl/ListDownloadableCommits.aspx

Resources