Fabricio writes:
> Linux Slackware 13.1gcc 4.5.1
> This .so files works fine in older postgres's versions.Postgres has support
> for this, but postgres team says do not use it?
It's not whether the .so works, it's whether you can overwrite it while
it's already open in some process. I think yo
Linux Slackware 13.1gcc 4.5.1
This .so files works fine in older postgres's versions.Postgres has support for
this, but postgres team says do not use it?
thanks tom, regards...
> To: fabrix...@hotmail.com
> CC: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] PostgreSQL 9.0.2. This is a
Fabricio writes:
> A developer is writing a function in C code and when he makes some change and
> replace the old library with the new one and if run CREATE OR REPLACE
> FUNCTION Postgre crash and restart. After restart CREATE OR REPLACE FUNCTION
> does not crash postgres, only the first time.
Achilleas Mantzios wrote:
> I agree about the subject line. But whouldn't -bugs be a more
> apropriate place than -performance?
Is it returning incorrect results, or is it not running as fast as
you would like?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To mak
Στις Friday 14 January 2011 23:20:25 ο/η Kevin Grittner έγραψε:
> Achilleas Mantzios wrote:
>
> > What i am asking is ways to understand what is going on, and what
> > to expect when i will have to actually perform the production
> > upgrade to 9.0.2
>
> Sorry to have focused on the wrong issu
This is a bug?
A developer is writing a function in C code and when he makes some change and
replace the old library with the new one and if run CREATE OR REPLACE FUNCTION
Postgre crash and restart. After restart CREATE OR REPLACE FUNCTION does not
crash postgres, only the first time. He
Achilleas Mantzios wrote:
> What i am asking is ways to understand what is going on, and what
> to expect when i will have to actually perform the production
> upgrade to 9.0.2
Sorry to have focused on the wrong issues from your latest post.
Here's what I suggest to try to get you the best in
Στις Friday 14 January 2011 22:06:56 ο/η Kevin Grittner έγραψε:
> Achilleas Mantzios wrote:
>
> > The other form (NOT IN) is the problem (in the case of
> > postgresql-9.0.2). (in 8.3 both queries are fast)
>
> So running EXPLAIN ANALYZE for this plan on the 9.0 version checks
> the time in m
Στις Friday 14 January 2011 22:06:56 ο/η Kevin Grittner έγραψε:
> Achilleas Mantzios wrote:
>
> > The other form (NOT IN) is the problem (in the case of
> > postgresql-9.0.2). (in 8.3 both queries are fast)
>
> So running EXPLAIN ANALYZE for this plan on the 9.0 version checks
> the time in m
Silvio Brandani wrote:
> I try to change odbc drivers (version 8.x to 9.x) and postgres
> version (8.3.x to 9.x , Linux platform ) but the error appear in
> all versions.
>MessageContext: 1590689792 total in 211 blocks; 8496 free (19
> chunks); 1590681296 used
Exact versions might be s
Achilleas Mantzios wrote:
> The other form (NOT IN) is the problem (in the case of
> postgresql-9.0.2). (in 8.3 both queries are fast)
So running EXPLAIN ANALYZE for this plan on the 9.0 version checks
the time in more places than the 8.3 version. For a plan that's an
order of magnitude slow
Not sure if this is the right list, and you probably know about this
already, was wondering if there's a fix imminent:
After installing postgresql-9.0.1-1-windows.exe on 64-bit windows 7, the
'postgres' user is visible as a new user that allows screen logins. I
looked into this and it's becau
Στις Friday 14 January 2011 16:41:18 γράψατε:
> Achilleas Mantzios wrote:
>
> > and NOT EXISTS
> >(SELECT distinct mold.id from marinerstates
>
> Does that do better if you leave out the DISTINCT keyword? Maybe
> use * instead of the column name?
Its already really fast, it doesn't matt
Στις Friday 14 January 2011 16:41:18 γράψατε:
> Achilleas Mantzios wrote:
>
> > and NOT EXISTS
> >(SELECT distinct mold.id from marinerstates
>
> Does that do better if you leave out the DISTINCT keyword? Maybe
> use * instead of the column name?
Its already really fast, it doesn't matt
Στις Friday 14 January 2011 16:41:18 γράψατε:
> Achilleas Mantzios wrote:
>
> > and NOT EXISTS
> >(SELECT distinct mold.id from marinerstates
>
> Does that do better if you leave out the DISTINCT keyword? Maybe
> use * instead of the column name?
Its already really fast, it doesn't matt
Achilleas Mantzios wrote:
> and NOT EXISTS
>(SELECT distinct mold.id from marinerstates
Does that do better if you leave out the DISTINCT keyword? Maybe
use * instead of the column name?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your
On Fri, Jan 14, 2011 at 12:57 AM, David Bear wrote:
> While running a yum update on a system, the update fails with the message:
>
> Transaction Check Error:
> package postgresql-libs-8.3.11-1PGDG.el5.x86_64 (which is newer than
> postgresql-libs-8.1.22-1.el5_5.1.i386) is already installed
>
>
Στις Thursday 13 January 2011 16:13:23 ο/η Achilleas Mantzios έγραψε:
>
> Next step, if i am lucky tonight, i'll set up a new linux box with 9.0.2 and
> load
> the same small (coming from FBSD_DEV) database.
>
> So my problem was twofold : a) EXPLAIN ANALYZE performance, b) the particular
> sl
Still problems of Out of Memory:
the query is the following and if I run it from psql is working fine,
but from application (through ODBC) I get error ,
I try to change odbc drivers (version 8.x to 9.x) and postgres version
(8.3.x to 9.x , Linux platform ) but the error appear in all versio
19 matches
Mail list logo
