On Thu, 2007-08-23 at 19:08 -0700, Postgres User wrote:
> On 8/23/07, Michael Glaesemann <[EMAIL PROTECTED]> wrote:
> >
> > On Aug 23, 2007, at 20:01 , Postgres User wrote:
> >
> > >>> Yes, I read the manual. I think I had a problem because of the
> > >>> special chars (< / >) that I'm trying to s
> Both tests were run over the network.
Okay. From what you mention above, it's likely that what you're seeing is a
bad query plan choice anyway.
ATB,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 6
ng at the differences in CPU usage, could it be that when you run your
query in psql, you are running psql on the database server itself while your
application is running on a separate server and sends its queries over the
network? If so, the extra CPU usage may be involved with sending/receiving
. 1.3.6 has
several important memory-leak fixes IIRC.
HTH,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
--
Sent via pgsql-general mailing list (pgsql-general@postgresq
lows the C caller to
retrieve the related error string.
While it does seem quite inelegant, I don't believe any problems linking
between C/C++ have been reported on any compiler/platform since this was
put into place.
HTH,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
Postg
ite a
few other open source GIS packages, I'd say quite small unless it was a
very minimal change. I also should point out that I have very little C++
experience, and so would be the wrong person to ask ;)
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - Post
Is mingw even fully supported on 64-bit today?
The mingw-w64 fork is fairly mature at the moment, and the devs are
really helpful if you do happen to find something that doesn't work. The
orignal mingw project 64-bit support is not that great.
http://mingw-w64.sourceforge.net/
ATB,
Mark
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
y applying the patch
here: http://code.google.com/p/postgis/issues/detail?id=43 and reporting
back whether it helps or not?
ATB,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
implements the OGC SFS for geometries and is compatible with a large
number of open source viewers/tools such as Mapserver, Geoserver, QGIS,
OGR etc...
ATB,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
--
Sent via pgsql
you may find the wiki at
http://postgis.refractions.net/support/wiki/ is a good starting point
for code examples.
ATB,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
--
Sent via pgsql-general mailing list (pgsql-general@postgresq
So the part I'm not sure is why the revision_files_revision_id_idx index
is favoured over revision_files_file_id_idx when LIMIT 1 is present?
AFAICT the planner should favour the index scan on file_id given that
the estimated cost in the second query is much lower than the one
estimate
e
application performing as expected so I'll have to stick with it.
ATB,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subs
e question over and over, I'm new at
this. Happy New Year, mine would be much happier if I could have this
all installed now!!
From what you've reported, it does seem that you're struggling somewhat
with the build process. I would second the suggestion that you add the
yum.pgsqlrpms
questions related to licensing, we would be glad
to discuss this further on the postgis-users mailing list.
Kind regards,
Mark.
(Member of the PostGIS PSC)
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusi
Hi everyone,
I've just got back from LinuxWorld in London and seeing this thread thought
I would share my experience of the MySQL stand - if you are of a delicate
dispostion, please look away now. I basically asked them straight up why I
should use MySQL instead of PostgreSQL and was quite surpris
> Hi all,
>
>
>
> I have a postgres installation thats running under 70-80% CPU usage
> while
>
> an MSSQL7 installation did 'roughly' the same thing with 1-2% CPU load.
>
>
>
> Here's the scenario,
>
> 300 queries/second
>
> Server: Postgres 8.1.4 on win2k server
>
> CPU: Dual Xeon 3.6 Ghz,
>
> Me
Hi everyone,
We're looking at investing in a new storage system in order to run
PostgreSQL and the advice we are getting is to move away from our current
SAN solution to a NAS solution. Can anyone offer any advice/experience on
using NAS devices to run a PostgreSQL database?
I have seen posts on
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 16 January 2004 21:50
> To: Martin Hampl
> Cc: [EMAIL PROTECTED]; Mark Cave-Ayland
> Subject: Re: [GENERAL] indexing with lower(...) -> queries
> are not optimised very well - Please He
he entire set
RETURN;
END
' LANGUAGE 'plpgsql';
If this is not possible, can anyone else suggest a way of getting the
required result?
Many thanks,
Mark.
---
Mark Cave-Ayland
Webbased Ltd.
Tamar Science Park
Derriford
Plymouth
PL6 8BX
England
Tel: +44 (0)1752 764445
Fax:
> -Original Message-
> From: DeJuan Jackson [mailto:[EMAIL PROTECTED]
> Sent: 04 August 2004 17:56
> To: Mark Cave-Ayland
> Cc: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] Recursive PLPGSQL function?
>
>
> If I'm not mistaken you have an infinit rec
done to
pg_upgrade between versions, since the only changes between versions
would be to provide the mappings between the on-disk structures of the
existing files (which could easily be determined by parsing the metadata
from the existing files) and the modified on-disk structure required by
the new ver
22 matches
Mail list logo