Re: Issue with Postgres process startup after instance restart
Hi Tom, I forgot to mention, but in this case it looks the mount was completed before the PG process was started up. But we don't have an explicit check for making sure the file system is present in the start script. Thanks for the tip. On Fri, 27 Mar 2020 at 19:30, Tom Lane wrote: > Shishir Joshi writes: > > I recently faced an issue with PG 11 where the VM that the PG process was > > running on got restarted because of a hardware issue. After the VM > restart, > > the Postgres process failed to start on the 1st attempt with the error > "*LOG: > > could not open directory "pg_tblspc/16388/PG_11_201809051": No such file > > or directory*" even though that directory was present. But on the 2nd > > attempt it started up without issues. There didn't seem to be any disk > > corruption issues and there were no other errors in the syslog either. > Has > > anyone else faced such an issue or has any ideas on why this could have > > occurred? > > Maybe whatever the tablespace is pointing at wasn't mounted yet? > Slow remote mounts are the bane of PG DBAs --- I can recall at least > one famous incident in which someone's database became totally > corrupt because the NFS mount it was on came up after server start, > leading to the server having a mishmash of files on the NFS server > and files on the local disk, now hidden underneath the mount point. > > If this is what your issue was, you got very lucky to escape without > damage. Suggest adapting your PG server start script to make sure the > mounted file system is present before you allow the server to start. > > regards, tom lane >
Uploading existing shapefile from geoserver to postgresql
Hi, Few weeks back, I upload my data (shapefile) directly to the geoserver. Last week, I just installed postgresql. How can I link the existing file in geoserver (shapefiles) to postgres using pgAdmin 4. Regards, Aisar
Re: Issue with Postgres process startup after instance restart
On Mon, 2020-03-30 at 11:02 +0530, Shishir Joshi wrote: > On Fri, 27 Mar 2020 at 19:30, Tom Lane wrote: > > Shishir Joshi writes: > > > I recently faced an issue with PG 11 where the VM that the PG process was > > > running on got restarted because of a hardware issue. After the VM > > > restart, > > > the Postgres process failed to start on the 1st attempt with the error > > > "*LOG: > > > could not open directory "pg_tblspc/16388/PG_11_201809051": No such file > > > or directory*" even though that directory was present. But on the 2nd > > > attempt it started up without issues. There didn't seem to be any disk > > > corruption issues and there were no other errors in the syslog either. Has > > > anyone else faced such an issue or has any ideas on why this could have > > > occurred? > > > > Maybe whatever the tablespace is pointing at wasn't mounted yet? > > Slow remote mounts are the bane of PG DBAs --- I can recall at least > > one famous incident in which someone's database became totally > > corrupt because the NFS mount it was on came up after server start, > > leading to the server having a mishmash of files on the NFS server > > and files on the local disk, now hidden underneath the mount point. > > > > If this is what your issue was, you got very lucky to escape without > > damage. Suggest adapting your PG server start script to make sure the > > mounted file system is present before you allow the server to start. > > I forgot to mention, but in this case it looks the mount was completed before > the PG process was started up. But we don't have an explicit check for making > sure the file system is present in the start script. Thanks for the tip. If that is an NFS mount, make sure it is "fg", not "bg". Also, check that your startup script simply fails if the file system is not mounted yet, rather than automatically running "initdb". Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
Good evening from Singapore, Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? Because I have never used PostgreSQL before. I am looking forward to hearing from you soon. Thank you. -BEGIN EMAIL SIGNATURE- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -END EMAIL SIGNATURE-
Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
po 30. 3. 2020 v 14:49 odesílatel Turritopsis Dohrnii Teo En Ming < c...@teo-en-ming.com> napsal: > Good evening from Singapore, > > Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? > > Because I have never used PostgreSQL before. > > I am looking forward to hearing from you soon. > Some database commands are same, or similar. Some are absolutely different. It depends Regards Pavel > Thank you. > > > > > > > > -BEGIN EMAIL SIGNATURE- > > The Gospel for all Targeted Individuals (TIs): > > [The New York Times] Microwave Weapons Are Prime Suspect in Ills of > U.S. Embassy Workers > > Link: > https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html > > > > > Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic > Qualifications as at 14 Feb 2019 and refugee seeking attempts at the > United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug > 2019) and Australia (25 Dec 2019 to 9 Jan 2020): > > [1] https://tdtemcerts.wordpress.com/ > > [2] https://tdtemcerts.blogspot.sg/ > > [3] https://www.scribd.com/user/270125049/Teo-En-Ming > > -END EMAIL SIGNATURE- > > >
Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
On 2020-03-30 21:03, Pavel Stehule wrote: po 30. 3. 2020 v 14:49 odesílatel Turritopsis Dohrnii Teo En Ming napsal: Good evening from Singapore, Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? Because I have never used PostgreSQL before. I am looking forward to hearing from you soon. Some database commands are same, or similar. Some are absolutely different. It depends Noted with thanks. Regards Pavel Thank you. -BEGIN EMAIL SIGNATURE- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -END EMAIL SIGNATURE-
Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
po 30. 3. 2020 v 15:06 odesílatel Turritopsis Dohrnii Teo En Ming < c...@teo-en-ming.com> napsal: > On 2020-03-30 21:03, Pavel Stehule wrote: > > po 30. 3. 2020 v 14:49 odesílatel Turritopsis Dohrnii Teo En Ming > > napsal: > > > >> Good evening from Singapore, > >> > >> Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? > >> > >> Because I have never used PostgreSQL before. > >> > >> I am looking forward to hearing from you soon. > > > > Some database commands are same, or similar. Some are absolutely > > different. It depends > > > Noted with thanks. > > Postgres has good documentation https://www.postgresql.org/docs/12/tutorial.html Pavel > > > > > Regards > > > > Pavel > > > >> Thank you. > >> > > > -BEGIN EMAIL SIGNATURE- > > The Gospel for all Targeted Individuals (TIs): > > [The New York Times] Microwave Weapons Are Prime Suspect in Ills of > U.S. Embassy Workers > > Link: > https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html > > > > > Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic > Qualifications as at 14 Feb 2019 and refugee seeking attempts at the > United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug > 2019) and Australia (25 Dec 2019 to 9 Jan 2020): > > [1] https://tdtemcerts.wordpress.com/ > > [2] https://tdtemcerts.blogspot.sg/ > > [3] https://www.scribd.com/user/270125049/Teo-En-Ming > > -END EMAIL SIGNATURE- >
Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
Turritopsis Dohrnii Teo En Ming schreef op ma 30-03-2020 om 20:49 [+0800]: > Good evening from Singapore, > > Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? Unfortunately mysql/mariadb syntax differs in general more than others dbms from the iso/ansi sql standard. > > Because I have never used PostgreSQL before. So you might have to adapt a bit when leaving mysql/mariadb for another dbms. To start development you should be ok, if you want to migrate data, you might want to use a migration tool (or fdw) (instead of dumping mysql syntax into postgresql) > > I am looking forward to hearing from you soon. > > Thank you. > > > > > > > > -BEGIN EMAIL SIGNATURE- > > The Gospel for all Targeted Individuals (TIs): > > [The New York Times] Microwave Weapons Are Prime Suspect in Ills of > U.S. Embassy Workers > > Link: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nytimes.com%2F2018%2F09%2F01%2Fscience%2Fsonic-attack-cuba-microwave.html&data=02%7C01%7Cwim.bertels%40ucll.be%7Cb58a22dd7cca44dbff4f08d7d4a8c9d5%7Ce638861b15d94de6a65db48789ae1f08%7C0%7C0%7C637211694717781909&sdata=jjYYIaR9%2BT%2Bn5ZnZ10asrNYy29%2FOH1diXRa%2Fz73%2FeCc%3D&reserved=0 > > * > *** > > Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic > Qualifications as at 14 Feb 2019 and refugee seeking attempts at the > United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 > Aug > 2019) and Australia (25 Dec 2019 to 9 Jan 2020): > > [1] > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftdtemcerts.wordpress.com%2F&data=02%7C01%7Cwim.bertels%40ucll.be%7Cb58a22dd7cca44dbff4f08d7d4a8c9d5%7Ce638861b15d94de6a65db48789ae1f08%7C0%7C0%7C637211694717781909&sdata=7y%2F8jlQS2YBeXw%2BZ6114Adl7Vsh73teL8PmNWZd%2Fc8s%3D&reserved=0 > > [2] > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftdtemcerts.blogspot.sg%2F&data=02%7C01%7Cwim.bertels%40ucll.be%7Cb58a22dd7cca44dbff4f08d7d4a8c9d5%7Ce638861b15d94de6a65db48789ae1f08%7C0%7C0%7C637211694717781909&sdata=Z70%2BW5Q7OUXswXw5j4Lt85W2DyLSycu8d4FCc1s8pq8%3D&reserved=0 > > [3] > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.scribd.com%2Fuser%2F270125049%2FTeo-En-Ming&data=02%7C01%7Cwim.bertels%40ucll.be%7Cb58a22dd7cca44dbff4f08d7d4a8c9d5%7Ce638861b15d94de6a65db48789ae1f08%7C0%7C0%7C637211694717781909&sdata=Ug%2BqnOPc5bB4g1LrECXLIz8EOUKlvdDXF10%2BcUTfxTI%3D&reserved=0 > > -END EMAIL SIGNATURE- > > -- mvg, Wim Bertels -- Lector UC Leuven-Limburg -- For years a secret shame destroyed my peace-- I'd not read Eliot, Auden or MacNiece. But now I think a thought that brings me hope: Neither had Chaucer, Shakespeare, Milton, Pope. -- Justin Richardson.
Re: Uploading existing shapefile from geoserver to postgresql
On 3/29/20 10:33 PM, Aisar Afif Ahmad Norzan wrote: Hi, Few weeks back, I upload my data (shapefile) directly to the geoserver. Last week, I just installed postgresql. How can I link the existing file in geoserver (shapefiles) to postgres using pgAdmin 4. I assume by geoserver you mean: http://geoserver.org/ I have to believe if you are dealing with shape files you will need PostGIS: https://postgis.net/ which is an extension to Postgres. Then you could follow the instructions here: https://docs.geoserver.org/latest/en/user/data/database/postgis.html Regards, Aisar -- Adrian Klaver adrian.kla...@aklaver.com
Re: Hot standby from Debian to Windows
On 3/29/20 11:35 PM, Andrus wrote: Hi! Would it not be easier to just set up another Debian server, run binary replication Breaks occurs rarely, 0-2 times per year. I want try it first. Got it. Just thought it would be easier not to have to deal with cross OS issues. and put them behind something like pgpool? Backup server will use single core and minimal RAM. It may be needed 0-2 times per year. pgpool should switch to use it for production work only if main server does not respond. I havent found this feature in pgpool documentation (maybe missed). Here is one example: https://www.pgpool.net/docs/latest/en/html/example-watchdog.html Andrus. -- Adrian Klaver adrian.kla...@aklaver.com
Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore
On 3/29/20 2:47 PM, Andrus wrote: Hi! Same warning appears two times. This command execute by pg_restore probably causes this (harmless?) warning: What warning? pg_restore: WARNING: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" I cranked up a Windows 7 instance and tried to migrate a Postgres 11 database from Ubuntu and it failed on the CREATE DATABASE step because of this line in the dump file: CREATE DATABASE redmine WITH TEMPLATE = template0 ENCODING = 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8'; I ran this statemnt it in Windows 10 with Postgres 12 successfully. Result was: WARNING: could not determine encoding for locale "en_US.UTF-8": codeset is "CPUTF-8" WARNING: could not determine encoding for locale "en_US.UTF-8": codeset is "CPUTF-8" CREATE DATABASE Query returned successfully in 1 secs 75 msec. redmine database was created. I dont understand why it failed in your test. Not sure but: 1) I was on Windows 7 2) Using Postgres 11 3) My Windows skills have atrophied, especially with the Windows command line. When I manually changed it in the plain text version of the dump file to: CREATE DATABASE redmine WITH TEMPLATE = template0 ENCODING = 'UTF8' LC_COLLATE = 'English_United States.1252' LC_CTYPE = 'English_United States.1252'; I verifed that data was restored using pg_restore without manually changing anything. So was this the same for the database you originally posted about, it actually restored it just threw warnings? If so I misunderstood the situation and thought the database was not loading. Andrus. -- Adrian Klaver adrian.kla...@aklaver.com
Re: Hot standby from Debian to Windows
Hi! Got it. Just thought it would be easier not to have to deal with cross OS issues. Here is one example: https://www.pgpool.net/docs/latest/en/html/example-watchdog.html Hopefully Windows Hyper-V virtual network adapter will not check windows 20 connection limit. In this case using Debian+Hyper-V+ binary replication allows to connect more than 20 users and may be best solution. Both have 64-bit OS. Will binary replication work in this case. Andrus.
Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore
Hi! Not sure but: 1) I was on Windows 7 2) Using Postgres 11 3) My Windows skills have atrophied, especially with the Windows command line. So was this the same for the database you originally posted about, it actually restored it just threw warnings? Looks like it restored. I havent checked restored data. If so I misunderstood the situation and thought the database was not loading. I tried CREATE DATABASE redmine WITH ENCODING = 'UTF8' LC_COLLATE = 'foo' LC_CTYPE = 'bar' template template0 in Linux and in Windows using Postgres 12.2 In Linux it throws error ERROR: invalid locale name: "foo" In Windows it creates database and throws warning only. Without template template0 clause it throws error in Windows also. In Linux CREATE DATABASE redmine WITH TEMPLATE = template0 ENCODING = 'UTF8' LC_COLLATE = 'English_United States.1252' LC_CTYPE = 'English_United States.1252'; also throws error ERROR: invalid locale name: "English_United States.1252" So it looks like pg_dump/pg_restore with --create works only from Linux to Windows and does not work from Windows to Linux. I expect that it should work from Windows to Linux also. Andrus.
Re: Hot standby from Debian to Windows
On 3/30/20 11:06 AM, Andrus wrote: Hi! Got it. Just thought it would be easier not to have to deal with cross OS issues. Here is one example: https://www.pgpool.net/docs/latest/en/html/example-watchdog.html Hopefully Windows Hyper-V virtual network adapter will not check windows 20 connection limit. In this case using Debian+Hyper-V+ binary replication allows to connect more than 20 users and may be best solution. That is something I would verify. It would surprise me if MS would allow you to turn a desktop OS(Windows 10) into a server OS. Both have 64-bit OS. Will binary replication work in this case. Take a look at: https://www.postgresql.org/docs/12/warm-standby.html#STANDBY-PLANNING It is not specifically ruled out, nor is it is explicitly ruled in. Myself, I would not bet on it being stable. Andrus. -- Adrian Klaver adrian.kla...@aklaver.com
Re: Hot standby from Debian to Windows
On 3/30/20 11:36 AM, Adrian Klaver wrote: On 3/30/20 11:06 AM, Andrus wrote: Hi! Got it. Just thought it would be easier not to have to deal with cross OS issues. Here is one example: https://www.pgpool.net/docs/latest/en/html/example-watchdog.html Hopefully Windows Hyper-V virtual network adapter will not check windows 20 connection limit. In this case using Debian+Hyper-V+ binary replication allows to connect more than 20 users and may be best solution. That is something I would verify. It would surprise me if MS would allow you to turn a desktop OS(Windows 10) into a server OS. Both have 64-bit OS. Will binary replication work in this case. Take a look at: https://www.postgresql.org/docs/12/warm-standby.html#STANDBY-PLANNING It is not specifically ruled out, nor is it is explicitly ruled in. Myself, I would not bet on it being stable. Clarification. The above was based on running Postgres under Windows itself. My mind had not updated to the Postgres on Debian in Hyper-V plan. In that case I would not see an issue. Andrus. -- Adrian Klaver adrian.kla...@aklaver.com
Re: Mixed Locales and Upgrading
On Sun, Mar 22, 2020 at 4:48 PM Don Seiler wrote: > > Here's the fun part. A lot of the tables use UUIDv4 strings for primary > keys. However these are stored in text/varchar columns. > Actually, would I need to re-index on text columns that we know contain UUID strings? UUID characters seem to be pretty basic alphanumeric ASCII characters. -- Don Seiler www.seiler.us
Re: Mixed Locales and Upgrading
Don Seiler writes: > Actually, would I need to re-index on text columns that we know contain > UUID strings? UUID characters seem to be pretty basic alphanumeric ASCII > characters. I think you're all right with respect to those, since they're the same under any encoding. It's columns containing non-ASCII characters that you'd want to worry about reindexing. regards, tom lane
Re: Mixed Locales and Upgrading
On Mon, Mar 30, 2020 at 4:30 PM Tom Lane wrote: > Don Seiler writes: > > Actually, would I need to re-index on text columns that we know contain > > UUID strings? UUID characters seem to be pretty basic alphanumeric ASCII > > characters. > > I think you're all right with respect to those, since they're the > same under any encoding. It's columns containing non-ASCII characters > that you'd want to worry about reindexing. > That's what I was hoping to hear. Thanks! Don. -- Don Seiler www.seiler.us
RE: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
From: Turritopsis Dohrnii Teo En Ming > Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? If you stuck to "standard SQL" in Mysql, you'll generally be fine; the differences will be pretty minor. The further you strayed from the standard will cause you more work -- usually. That being said, moving for any DB to another will always cause you to find DB-specific things. Of course, there are always a few things that can only be done with DB-specific code, so you'll be rewriting those parts with certainty (an example is the insert-or-update concept). [Side note: I forced myself to read a good part of the SQL standard some time back and was amazed by how many times the phrase "implementation defined" was used, which helps to explain why all the DBs do some things so differently.] The admin commands are quite different as well, be prepared for that, but I can't think of anything that Mysql can do that Pg can't as well. (Although it's been awhile since I had to use Mysql, so I may have forgotten something.) Last but not least, please remember that all of those "unusual" things you had to do to get Mysql to work, or work around its bugs, won't be needed and will more than likely get in your way with Postgresql. I'm not saying the Pg is perfect, but that Mysql's bugs and oddities don't apply to Pg. Good luck with your conversion and welcome to Pg! Kevin This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, distribution, review, copy or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify us by reply e-mail, and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you.
Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
On 2020-03-30 21:26, Wim Bertels wrote: Turritopsis Dohrnii Teo En Ming schreef op ma 30-03-2020 om 20:49 [+0800]: Good evening from Singapore, Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? Unfortunately mysql/mariadb syntax differs in general more than others dbms from the iso/ansi sql standard. Because I have never used PostgreSQL before. So you might have to adapt a bit when leaving mysql/mariadb for another dbms. To start development you should be ok, if you want to migrate data, you might want to use a migration tool (or fdw) (instead of dumping mysql syntax into postgresql) I have had more exposure to MySQL/MariaDB in the past. I am looking forward to hearing from you soon. Thank you. -- mvg, Wim Bertels -- Lector UC Leuven-Limburg -- For years a secret shame destroyed my peace-- I'd not read Eliot, Auden or MacNiece. But now I think a thought that brings me hope: Neither had Chaucer, Shakespeare, Milton, Pope. -- Justin Richardson. -BEGIN EMAIL SIGNATURE- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -END EMAIL SIGNATURE-
Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
On 2020-03-31 06:30, Kevin Brannen wrote: From: Turritopsis Dohrnii Teo En Ming Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? If you stuck to "standard SQL" in Mysql, you'll generally be fine; the differences will be pretty minor. The further you strayed from the standard will cause you more work -- usually. That being said, moving for any DB to another will always cause you to find DB-specific things. Of course, there are always a few things that can only be done with DB-specific code, so you'll be rewriting those parts with certainty (an example is the insert-or-update concept). [Side note: I forced myself to read a good part of the SQL standard some time back and was amazed by how many times the phrase "implementation defined" was used, which helps to explain why all the DBs do some things so differently.] The admin commands are quite different as well, be prepared for that, but I can't think of anything that Mysql can do that Pg can't as well. (Although it's been awhile since I had to use Mysql, so I may have forgotten something.) Last but not least, please remember that all of those "unusual" things you had to do to get Mysql to work, or work around its bugs, won't be needed and will more than likely get in your way with Postgresql. I'm not saying the Pg is perfect, but that Mysql's bugs and oddities don't apply to Pg. Good luck with your conversion and welcome to Pg! Kevin Noted with thanks. -BEGIN EMAIL SIGNATURE- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -END EMAIL SIGNATURE-
Re: PG12 autovac issues
On Sat, Mar 28, 2020 at 05:53:59PM +0900, Michael Paquier wrote: > And I'll follow up there with anything new I find. Please let me know > if there are any objections with the revert though, this will address > the problem reported by Justin. Okay. Done with this part now as of dd9ac7d. Now for the older issue.. -- Michael signature.asc Description: PGP signature
Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
One thing that is different about Postgres is that it uses a lot of "meta-commands". https://www.postgresql.org/docs/current/app-psql.html An important one is "\q", which exits you from the database. Typing "quit" or "exit" won't get you out of the session. = Eric MacAdie On Mon, Mar 30, 2020 at 11:16 PM Turritopsis Dohrnii Teo En Ming wrote: > > On 2020-03-30 21:26, Wim Bertels wrote: > > Turritopsis Dohrnii Teo En Ming schreef op ma 30-03-2020 om 20:49 > > [+0800]: > >> Good evening from Singapore, > >> > >> Is PostgreSQL SQL database command syntax similar to MySQL/MariaDB? > > > > Unfortunately mysql/mariadb syntax differs in general more than others > > dbms from the iso/ansi sql standard. > > > >> > >> Because I have never used PostgreSQL before. > > > > So you might have to adapt a bit when leaving mysql/mariadb for another > > dbms. To start development you should be ok, > > if you want to migrate data, you might want to use a migration tool (or > > fdw) (instead of dumping mysql syntax into postgresql) > > I have had more exposure to MySQL/MariaDB in the past. > > > > > >> > >> I am looking forward to hearing from you soon. > >> > >> Thank you. > >> > >> > >> > >> > >> > >> > >> > > >> > >> > > -- > > mvg, > > Wim Bertels > > -- > > Lector > > UC Leuven-Limburg > > -- > > For years a secret shame destroyed my peace-- > > I'd not read Eliot, Auden or MacNiece. > > But now I think a thought that brings me hope: > > Neither had Chaucer, Shakespeare, Milton, Pope. > > -- Justin Richardson. > > > -BEGIN EMAIL SIGNATURE- > > The Gospel for all Targeted Individuals (TIs): > > [The New York Times] Microwave Weapons Are Prime Suspect in Ills of > U.S. Embassy Workers > > Link: > https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html > > > > Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic > Qualifications as at 14 Feb 2019 and refugee seeking attempts at the > United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug > 2019) and Australia (25 Dec 2019 to 9 Jan 2020): > > [1] https://tdtemcerts.wordpress.com/ > > [2] https://tdtemcerts.blogspot.sg/ > > [3] https://www.scribd.com/user/270125049/Teo-En-Ming > > -END EMAIL SIGNATURE- > >
Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?
Eric MacAdie writes: > One thing that is different about Postgres is that it uses a lot of > "meta-commands". > https://www.postgresql.org/docs/current/app-psql.html > An important one is "\q", which exits you from the database. Typing > "quit" or "exit" won't get you out of the session. Actually, since v11 that does work ... a concession we've made to MySQL converts ;-) regards, tom lane
