> From: Richard Huxton [mailto:[EMAIL PROTECTED]
> > MessageContext: 1946198040 total in 258 blocks; 26624 free (43
> > chunks);
> > 1946171416 used
>
> Well, I don't have to be a developer to know that if there's
> a memory problem it's that big number starting 1946... that's
> the problem. I
> From: Richard Huxton [mailto:[EMAIL PROTECTED]
>
> Relyea, Mike wrote:
>> If I execute this query in PGAdmin III it runs without any errors and
returns no records.
>
> Hmm. So what's different about the queries?
>
Nothing. The SQL is identical. I copied o
> From: Richard Huxton [mailto:[EMAIL PROTECTED]
> Relyea, Mike wrote:
> > This seems to be a problem with the ODBC driver? How can I narrow
> > that down further?
>
> Well, first make 100% certain the query being executed is the
> one you see being sent from A
> From: Richard Huxton [mailto:[EMAIL PROTECTED]
> Relyea, Mike wrote:
> > This seems to be a problem with the ODBC driver? How can I narrow
> > that down further?
>
> Well, first make 100% certain the query being executed is the
> one you see being sent fro
Since we upgraded from postgres 8.0 to 8.4, every script where we have queries
that use temp tables now has to have an explicit drop of the temp table at the
end of the script, or it will blow up the next time it runs, saying it cannot
create the temp table because it already exists (these are c
I need help understanding what I'm doing wrong with an insert statement.
I'm running 8.3.7 on Windows and the DB is complaining about the select
statement in my insert statement.
I'm trying to execute
DROP TABLE IF EXISTS "tblTempSpecs";
CREATE TEMP TABLE "tblTempSpecs" AS SELECT "tblSpecs"."Cart
> From: bricklen [mailto:brick...@gmail.com]
> Sent: Thursday, July 16, 2009 4:05 PM
> To: Relyea, Mike
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Error in insert statement
>
> Try dropping the word "VALUES".
>
> eg.
> INSERT INTO
> From: pgsql-general-ow...@postgresql.org
> [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of
> Thomas Kellerer
> Sent: Thursday, July 16, 2009 4:05 PM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Error in insert statement
>
> Relyea, Mike wrote on
> -Original Message-
> From: pgsql-general-ow...@postgresql.org
> [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Joshua Berry
> Sent: Tuesday, May 05, 2009 10:39 AM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Converting Rows to Columns
>
> Greetings all,
>
> I know
I need to create my very first function. I'm using 8.0.2 and I need a
function that I can call (from my client app) with an unknown number of
criteria for a select query. The function will then return the results
of the query. In my mind, it would go something like what I've outlined
below. I r
)
INNER JOIN "tblBlockAC"
ON "Targets"."TargetID" = "tblBlockAC"."TargetID"
WHERE (("PrintSamples"."MachineID" = '2167' OR
"PrintSamples"."MachineID" = '2168' OR "PrintSample
I'm currently building an
Access FE to my PostgreSQL BE. So far it works great. If you're
going to be deploying this to multiple users, I'd suggest using a DSN-less
connection. That way you don't have to set up a DSN on each user's
PC.
Mike
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROT
FWIW, I'm using
PostgreSQL on Windows with an Access/VBA FE that is currently under
development. My PostgreSQL BE has 29 tables and several of them
currently have anywhere from 1 to 8 million records and growing. For me,
Access was really the only choice. In our corporate environment, eve
I do the same thing with DAO and changing my querydef at run time, but I've
added a few 'enhancements'. First, I use a DSNLess connection - that way I
don't have to set up a DSN on each client's PC. Check out
http://gborg.postgresql.org/project/psqlodbc/genpage.php?howto-accessvba for
more in
I am trying to optimize a delete query that's currently taking 4 hours
to run. My first step was to add some indexes on some of my FK's. That
sped up my select queries by as much as ~20x. From 3.5 sec to < 0.25
sec. They didn't help my delete query. I ran an explain analyze on the
delete query
Given my query:
SELECT "PrintSamples"."MachineID" , "PrintSamples"."PrintCopyID" ,
"tblColors"."Color" , "tblBlockAC"."AreaCoverage" ,
"tblFriendlyParameterNames"."FriendlyParameterName" AS "Measurement" ,
"ParameterValues"."ParameterValue" AS "V
I knew I would forget to include some obvious info. I'm running PG
8.0.x on WinXP and have vacuum full analyzed.
-Original Message-
From: Relyea, Mike
Sent: Monday, June 27, 2005 5:10 PM
To: 'pgsql-general@postgresql.org'
Subject: Indexes not used - what am I missing?
That's because they don't exist. You need to create them. I did it on
WinXP and it works fine.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zlatko Matic
Sent: Tuesday, June 28, 2005 9:08 AM
To: Magnus Hagander; Andreas; pgsql-general@postgresql.org
Su
night, so I run my maintenance then.
Name-Of-File-With-Maintenance-Commands contains SQL to refresh a
materialized view and do a vacuum full analyze
-Original Message-
From: Zlatko Matic [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 28, 2005 1:07 PM
To: Relyea, Mike; pgsql-general@postgr
I don't know what OS you're using, but I recently went through the same
search on a very tight budget (free). I ended up using Visio because I
already had it. I have Visio 2002 but found out that the standard
version that I have won't connect to an ODBC DB and generate an ERD.
However, the Pro ve
You only need to use quotes in your SQL statements if your table names
in PostgreSQL contain any upper case letters. PostgreSQL automatically
converts all of your SQL statements to lower case unless they're quoted.
As an alternative to quoting in VB (assuming you're using Access as your
FE), stor
As an alternate solution, what about using a pass through query? Access
won't mess with the SQL that way. I don't know if that will suit your
needs, but I tend to use them almost exclusively in my Access/PostgreSQL
project.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PRO
I've just started receiving an out of memory error with my most complex
query. It has been running fine for the past 9 months. It's a snapshot
materialized view that I update every night using the functions from
http://jonathangardner.net/PostgreSQL/materialized_views/matviews.html
The error I'm
work_mem = 262144
I'm still trying to figure out how to track the memory usage in
ExecutorState
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Sunday, June 18, 2006 11:13 PM
To: Qingqing Zhou
Cc: pgsql-general@postgresql.org
Subject: Re:
So what's my next step? How do I track down what is causing this
problem?
-Original Message-
From: Qingqing Zhou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 21, 2006 11:01 PM
To: Relyea, Mike
Cc: pgsql-general@postgresql.org; Tom Lane
Subject: RE: [GENERAL] Out of memory err
I've zipped the results of EXPLAIN INSERT INTO "tblSummary" SELECT *
FROM "qrySummary"; for my case. It's a zip file that I've renamed to
.txt in order to get around the attachment being blocked by certain mail
servers.
PK yÖ4¨yï ý explain.txtí]]oÇÕ¾/[EMAIL
PROTECTED]( É`ç{ÖH
Thanks Jim and Tom. At least now I've got a direction to head in. I
think for now I'll probably reduce work_mem as a stop-gap measure to get
the query running again. This will buy me some time to redesign it.
I'll probably separate out each sub query and store the results in a
table (would a tem
27 matches
Mail list logo
