Topic-icon PostgreSql installation problems

Active Subscriptions:

None
10 years 5 months ago #39671 by everburninglight
Ok, no problem. Thanks for extending my subscription. If you need, I can be a permanent Postgresql tester, hahaha.
The topic has been locked.
Support Specialist
10 years 5 months ago #39677 by alzander
You likely will be for a while. If you keep pushing back any fixes or bubbling up problems, we'll extend the subscription for a while more... likely not forever, but will do another 3 months when this period is almost up.

Having Postgres support is helping us, actually, as well. It's cleaning up some of our queries to make them more generic and making us analyze things a little differently. It also makes us a small hop away from adding MSSQL and other database support, which can help grow things a little.. not huge markets, but still good to promote too.

As for Postgres in general, do you mind letting us know why you chose it? Was it just what your server came with, or what you prefer to work with? Would love to hear your background and thoughts on it. It's definitely more strict than MySQL, which has it's advantages, but still not something commonly used.

Oh yeah, the v5.2.2 release slipped and should be out today. Had a few minor hiccups at the end of last week that pushed it back.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 5 months ago - 10 years 5 months ago #39680 by everburninglight
Simply, Postgresql is performing and fit for medium to big databases; Mysql is just a toy and is not reliable with something other than a small database.

I have other services on the same server with a database of about 1 GB. Postgresql needs almost 3 seconds to perform a simple query on my biggest table. Mysql will require 10 minutes.

For me, it was not worth to keep multiple databases and hog up the RAM of the server. Mysql is very resource intensive and suffers until it hangs with a higher traffic. Postgresql manages everything with little memory like a charm.

So, since I am on a VPS, my need is to save RAM and have always a responsive system in *any* condition, which I could obtain only with Postgresql. That's why I have been moving everything to Postgresql.
Last edit: 10 years 5 months ago by everburninglight.
The topic has been locked.
Support Specialist
10 years 5 months ago #39708 by alzander
Thanks for the explanation. I think MySQL can honestly scale past 1Gig databases pretty easily (we've seen that in the past on some of our own projects). Beyond that though, Postgres does have some stability features that I will agree with. I haven't looked into their memory footprint, but will have to evaluate more.

I appreciate the info.. will be good to look into more. As for Joomla support, it's seemed to be pretty stable on our testing of Postgres. Have you found decent extension compatibility as well? Hope you don't mind the questions!

Thanks again,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 5 months ago #39726 by everburninglight
Indeed, after 10 years of Mambo, upgrading the Debian distro broke everything up and forced us to build all the site again. We wrote many custom components for Mambo and used various extensions.
Now, with the new Joomla, we think just the opposite: just basic functions and the least extensions, to avoid future upgrade problems. We are pretty happy after tweaking with Joomla functions.

The only extension we used aside JFBConnect is Responsivizer, to have a mobile enabled site. We really tried many other solutions and none worked. Responsivizer had a couple of issues that pointed us to fix some code in Joomla. Now everything works perfectly and it is compatible with JFBConnect.
The topic has been locked.
Support Specialist
10 years 5 months ago #39737 by alzander
Using the least amount of extensions necessary is always a good way to go. Less conflicts, less 'migration' issues, and less extra stuff to make sure is up to date (and not insecure).

Interesting to hear you've been on Mambo for 10 years. Crazy! I've never even used Mambo. I started with Joomla right at the 1.0 -> 1.5 transition, so mostly got my feet wet with 1.5 and never adjusted/liked 1.0.

Anyways, I'm glad to hear that JFBConnect is working well for you on your site and Postgres. We'll be testing with it going forward, but won't have our automated suite of tests running on it for some time. That means that it's possible that a bug or 2 may creep in here or there.. the good news is that they should be easy to fix when/if that happens.

Thanks again for all the feedback. It's been very appreciated!
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 5 months ago #39750 by everburninglight
I installed v5.2.2 over the previous version and no errors so far. All main functions seem working. Other extensions have no conflict.
The topic has been locked.
Support Specialist
10 years 5 months ago #39758 by alzander
Fantastic! Thanks, as always, for the feedback. With all the updates to our DB queries, we were concerned that something may break in Postgres or MySQL. So far, just one minor error, and nothing that would require a new release for it yet... whew! :)

Best of luck,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 5 months ago #39761 by everburninglight
Found a problem. Again, this error happened: Database query failed (error # %s): %s SQL=SELECT * FROM joo_menu WHERE id=''

It happens when one tries to retrieve his username or reset his password. It seems that JFBConnect touches something of mod_sclogin. I reinstalled my modified version of the module and everything worked.
The topic has been locked.
Support Specialist
10 years 5 months ago #39788 by alzander
Can you let me know what change you made to the module that fixed that issue? I'm a bit confused on how those links are causing a database error. The SCLogin module (and JFBConnect for that matter) don't process the "Forgot xyz" links. We just create links that go to the Joomla User component. When clicked, the user is interacting with core Joomla, not our module or component.

We'll gladly investigate, just can't figure out where to begin on this one.

Thanks,
Alex
The topic has been locked.