active antivirus scanner, but we excluding the PostgreSQL folders
where are the data folder locate is.
Hope any one can help
Best regards
Tony
The following bug has been logged online:
Bug reference: 5696
Logged by: Tony Marston
Email address: t...@marston-home.demon.co.uk
PostgreSQL version: 9.0
Operating system: Widows XP
Description:cannot upgrade to 9.0.1
Details:
I have just installed version 9.0
The following bug has been logged online:
Bug reference: 5690
Logged by: Tony marston
Email address: t...@marston-home.demon.co.uk
PostgreSQL version: 9.0
Operating system: Windows XP
Description:pg_upgrade fails
Details:
I am trying to upgrade from version 8.4 to
nctionally dependent on any other column in
the GROUP BY clause. All you can do is point to paragraphs which are NOT
contained in the definition of the GROUP BY clause and say "this is our get
out". Now you wonder why I refer to your arguments as "weasel words".
Tony Marston
ht
something different?
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
> -Original Message-
> From: Greg Stark [mailto:[EMAIL PROTECTED] On
> Behalf Of Gregory Stark
> Sent: 15 October 2008 02:57
> To: Tony Marston
> Cc: 'Peter Eisentraut'; pg
not follow the standards". As soon as I point out an SQL
standard that you DON'T follow I get a barrage of weasel words and pathetic
excuses.
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
> -Original Message-
> From: Peter Eisentraut [mailto:[EMAIL PROTEC
The following bug has been logged online:
Bug reference: 4465
Logged by: Tony Marston
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Windows XP
Description:GROUP BY is not to SQL standard
Details:
The Postgresql implementation of GROUP
The following bug has been logged online:
Bug reference: 2850
Logged by: Tony Marston
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows XP
Description:Cannot select from information_schema.schemat
Details:
If I am logged on as a
The following bug has been logged online:
Bug reference: 2848
Logged by: Tony Marston
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows XP
Description:information_schema.key_column_usage does not work
Details:
I have the following
The following bug has been logged online:
Bug reference: 2125
Logged by: Tony
Email address: [EMAIL PROTECTED]
PostgreSQL version: 80100
Operating system: XP SP2
Description:SELECT problem with strings containing \
Details:
Hi,
Please refer to the DDL and data
The following bug has been logged online:
Bug reference: 2130
Logged by: Tony Marston
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: Windows XP
Description:missing FROM-clause entry for table "mnu_task"
Details:
An SQL query
Alvaro Herrera wrote:
> Stallone wrote:
>
> Please keep replies on the list.
>
>
>>What you have done is run a SELECT which evaluates the function
>>f_multiparam() passing it two parameters, and then takes the result and
>>puts it INTO a local parameter. This is not the same. An OUT parameter
The following bug has been logged online:
Bug reference: 2108
Logged by: Tony
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Debian 1:3.3.5-8ubuntu2, 2.6.10-5-k7, i686
Description:Function with OUT parameters not recognized, using
The following bug has been logged online:
Bug reference: 2107
Logged by: Tony S
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Debian 1:3.3.5-8ubuntu2, 2.6.10-5-k7, i686
Description:Function INOUT parameter not returned to caller, causes
The following bug has been logged online:
Bug reference: 1966
Logged by: Tony Caduto
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Linux
Description:Single OUT PARM does not return param name.
Details:
When creating a plpgsql function
(I found
> one where there is no exception thrown for the additional
> parameters; they are silently
> discarded.)
>
> -Kevin
>
> P.S. A more professional and cooperative tone in any future
> posts would be appreciated.
I will try.
Tony Marston
http://www.t
No, but Oracle does, which is why I am trying to produce SQL statements that
will run on MySQL, PostgreSQL and Oracle without the need for conversion.
Tony Marston
http://www.tonymarston.net
> -Original Message-
> From: Jim C. Nasby [mailto:[EMAIL PROTECTED]
> Sent: 10 Oct
translation performed by operating system or network utilities. Use this
function in applications that will be moved between environments with differing
character sets.
Tony Marston
http://www.tonymarston.net
pgman@candle.pha.pa.us wrote:
> Tony Marston wrote:
> > > which Oracle supports a
> -Original Message-
> From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
> Sent: 09 October 2005 17:42
> To: Tony Marston
> Cc: pgsql-bugs@postgresql.org; 'Stephan Szabo'
> Subject: Re: [BUGS] BUG #1937: Parts of information_schema
> only accessible to o
> -Original Message-
> From: David Fetter [mailto:[EMAIL PROTECTED]
> Sent: 09 October 2005 18:20
> To: Tony Marston
> Cc: 'Tom Lane'; 'Jim C. Nasby'; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1947: Enhancement Request - CONCAT() function
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2005 22:30
> To: Jim C. Nasby
> Cc: Tony Marston; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1947: Enhancement Request - CONCAT()
> function
>
>
> "Jim C
> -Original Message-
> From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2005 14:09
> To: Tony Marston
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1937: Parts of information_schema
> only accessible to owner
>
>
> Plea
> -Original Message-
> From: David Fetter [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2005 22:16
> To: Tony Marston
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1947: Enhancement Request - CONCAT() function
>
>
> On Sat, Oct 08, 2005 at 12:
> -Original Message-
> From: Stephan Szabo [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2005 18:01
> To: Tony Marston
> Cc: pgsql-bugs@postgresql.org
> Subject: RE: [BUGS] BUG #1937: Parts of information_schema
> only accessible to owner
>
>
>
> On Sa
> -Original Message-
> From: Stephan Szabo [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2005 16:44
> To: Tony Marston
> Subject: RE: [BUGS] BUG #1937: Parts of information_schema
> only accessible to owner
>
>
> On Sat, 8 Oct 2005, Tony Marston wrote:
>
The following bug has been logged online:
Bug reference: 1947
Logged by: Tony Marston
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Windows XP
Description:Enhancement Request - CONCAT() function
Details:
I would like the option to use
The following bug has been logged online:
Bug reference: 1937
Logged by: Tony Marston
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Windows XP
Description:Parts of information_schema only accessible to owner
Details:
I have been
s not seem to work exactly as expected, at
least with freshly restored functions from 7.x
I can run a SQL monitor that shows the exact SQL that is being sent to
the server, so I will do that and then
let you know.
Thanks for the response,
Tony Caduto
Peter Eisentraut wrote:
Tony Caduto wrote:
The following bug has been logged online:
Bug reference: 1375
Logged by: Tony Caduto
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Gentoo Linux
Description:Problem with Dollar qouting functions
Details:
I restored my 7.4.x database to
itself Explain
would always report the index being used, but when run in the context of
the function the indexes where not being used.
Thanks,
Tony Caduto
---(end of broadcast)---
TIP 8: explain analyze is your friend
varHoldingPercent );
END IF;
Thanks
Tony Caduto
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
not been changed or deleted. On
monday I am going to replace the count(*) with a for select and a
counter variable and see if the slowness goes away. It really does seem
to be some issue/bug maybe or just a difference in the 8.0 engine.
Thanks,
Tony Caduto
Tom Lane wrote:
Tony Caduto
Hi,
I just installed 8.0 RC1 and then restored my database which was working
perfectly on 7.4.5.
I have a function that imports rows from a comma seperated file and on
7.4.5 using this same function I could get around 1000 rows every 2.5
seconds, now with 8.0 RC1 this has gone way up and it seem
DB appears to be corrupted but cannot isolate cause, it has happened
multiple times after recreating database. The system seems stable otherwise
The message when trying to do
psql name_of_database:
NOTICE: RelationBuildDesc: can't open pg_statistic: No such file or
directory
ERROR: cannot open p
ike the \d command is not picking up the longer
NAMEDATALEN at compile time.
Tony
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
field "astext" is
8190.
Does this the PostgreSQL's ODBC problem? If
the ODBC can not get the field's size, would it give the size of
8190?
Or this is the PostGIS's problem?
Best regards,Tony
---Tony Jiang, MScResearch &
Development Programmer/AnalystMRF Geosyste
system will
be initialized with username "Tony".This user will own all the data files
and must also own the server process.
Fixing permissions on existing
directory /PGDATACreating directory /PGDATA/baseCreating directory
/PGDATA/globalCreating directory /PGDATA/pg_xlogCreating
field "astext" is
8190.
Does this the PostgreSQL's ODBC problem? If
the ODBC can not get the field's size, would it give the size of
8190?
Or this is the PostGIS's problem?
Best regards,Tony
---Tony Jiang, MScResearch &
Development Programmer/AnalystMRF Geos
. Obviously, this is not the limits of the PgSQL
itsself when using psql.
It is the PGLIB, isn't it?Is there any solution or
suggestion?Thanks.
Best regards,Tony
---Tony Jiang, MScResearch &
Development Programmer/AnalystMRF Geosystems Corp (www.mrf.com)Suite 700, 665 8th Street SW,
Ca
R "RI_ConstraintTrigger_64226" ON "test2";
DROP TRIGGER "RI_ConstraintTrigger_64228" ON "test1";
DROP TRIGGER "RI_ConstraintTrigger_64230" ON "test1";
After that I try to insert into table1:
INSERT INTO "test1" ("id", "su
40 matches
Mail list logo
