leakage; the symptoms
would be pretty obvious.
Have you poked into the client-side state to see what that end thinks
it's doing with the idle connections?
regards, tom lane
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
.
regards, tom lane
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
of the intended left join, or it won't work as desired.
Seems like a bit of a foot-gun ...
regards, tom lane
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Jan Pazdziora jpazdzi...@redhat.com writes:
On Sun, Nov 21, 2010 at 11:44:08AM -0500, Tom Lane wrote:
It's certainly not off by default in the stock postgresql84 package.
Is it possible that something in spacewalk changed it?
No. The installation instructions that we have for the PostgreSQL
-wiring them to integer.
regards, tom lane
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Jan Pazdziora jpazdzi...@redhat.com writes:
On Wed, Jul 21, 2010 at 06:21:04PM -0400, Tom Lane wrote:
Isn't s/sysdate/current_timestamp/g a good solution? That's standards
compliant, unlike sysdate.
I wouldn't dare to do that en masse. It's a different type --
timestamp instead of date, so
not pushed 4.0 into Fedora yet) but it'd be another
set of issues to face at some point.
regards, tom lane
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Jan Pazdziora jpazdzi...@redhat.com writes:
what are our possibilities for handling sysdate in PostgreSQL.
Isn't s/sysdate/current_timestamp/g a good solution? That's standards
compliant, unlike sysdate.
regards, tom lane
postgresql84 instead of
postgresql. (I think this also means that the original goal of
being able to run on PG 8.1 is a dead letter.)
Personally though I'm more interested in an F-13 build.
regards, tom lane
___
Spacewalk-devel
people are annoyed about it, there might be a
Postgres-only fork.
regards, tom lane
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Kevin Fox kevin@pnl.gov writes:
On Tue, 2010-05-04 at 12:26 -0700, Tom Lane wrote:
Indeed. I don't *want* to see a fork, I'm just pointing out that that
might happen if nothing gets done.
At the rate things are going, I doubt it. Space walk developers are
willing to accept postgres
sure by now the plpgsql version has
bitrotted from failure to track subsequent changes in the PL/SQL code.
regards, tom lane
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo
about compatibility to pre-8.4 Postgres versions,
which eliminates a number of the annoying syntax discrepancies.
I'm still happy to contribute Postgres-specific knowledge, but I can't
be the point man because I hardly know Spacewalk at all.
regards, tom lane
Jeff Ortel jor...@redhat.com writes:
Tom Lane wrote:
Perhaps we could use views as a PG substitute for synonyms?
Perhaps. My concern about using views even as an interim solution is
that the monitoring code has high insert/update demands (I'm assuming)
and we'd have to use 'on insert/update
an actually usable pgsql port? Last I
heard there were still uncompleted tasks as far as installation went.
regards, tom lane
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk
? I agree
with the idea of getting rid of them over the long term, but it would be
nice to not have that in the critical path if there is a lot of code
that would have to change.
regards, tom lane
___
Spacewalk-devel mailing list
Matej Hasul matej.ha...@gmail.com writes:
Hello, I started working on migrating tables to mysql.
Isn't this a complete waste of time? There is exactly 0 chance of
migrating all those procedures to mysql.
regards, tom lane
=?ISO-8859-2?Q?Miroslav_Such=FD?= msu...@redhat.com writes:
Tom Lane wrote:
Isn't this a complete waste of time? There is exactly 0 chance of
migrating all those procedures to mysql.
How do you know?
Try it for awhile and see what you think. The incompatibilities and
missing features
18 matches
Mail list logo
