Re: [GENERAL] stats collector appears to be dying

2005-02-24 Thread Magnus Hagander
I'm having an issue with what appears to be the stats collector process dying on Postgresql 8.0.1 running on Windows XP w/sp1. I've enabled stats_command_string and stats_row_level in my config file. During bulk inserts the stats collector process appears to encounter some sort of

Re: [GENERAL] maximum size

2005-02-24 Thread Richard Huxton
Molinet Sylviane wrote: Hello, could you be so kind to help me with following requests ? I need the maximum size of the following types : varchar(n) numeric(n,p) text bytea Could you please give me the name of articles or publications and where I can find it for these requests ? Well, the manuals

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Ron Mayer
On Wed, 23 Feb 2005, Tom Lane wrote: Ron Mayer [EMAIL PROTECTED] writes: +if (needed MaxFSMPages)... ereport(WARNING, ... An unconditional WARNING seems a bit strong to me for a case that is not necessarily wrong. How about a HINT, not unlike the checkpoints are occurring too

Re: [GENERAL] Scalability with large numbers of tables

2005-02-24 Thread Thomas F.O'Connell
To me, the issues of scalability come from a management perspective. I'm dealing with a schema that has tens of thousands of tables, but they are inherited from a relatively small set of superclass tables. I imagine there are similar issues to managing schemas as there are to managing subclass

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Christopher Kings-Lynne
I find this tiny (9-line) patch useful to help my clients know when FSM settings may need updating. Some of the more frequently asked questions here are in regards to FSM settings. One hint I've seen is to run vacuum verbose;. At the end of thousands of lines of INFO and DETAIL messages

[GENERAL] racing of tables deleting - how?

2005-02-24 Thread mef
Hello, pgsql-general :) I need to make a some actions on 'deleting table' event. It event my be raise both stored procederes and any other's ways (pgAdmin GUI for example). Is any solutions for trace it and execute some actions before/after deleting. I try to create trigger on pg_class

[GENERAL] Report of some problem under PL/PGSQL 7.4.7 8.0.1

2005-02-24 Thread Froggy / Froggy Corp.
Hi everyone, I made a tetris under pl/pgsql and i encounter some problem with this non commun use of pl/pgsql. For each problem, i didn't see information about them, so my report : - Array problem (7.4.7 8.0.1) : I got a lot of problem with using array, like i saw under the ML,

Re: [GENERAL] Fedora postgresql not starting

2005-02-24 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Thu, 24 Feb 2005, Ulrich Wisser wrote: I installed the latest postgresql packages on my Fedora Core 3 box. Is it Red Hat RPMs or RPMs? 8.0.1 or 7.4.7? PG will not start, even initdb on a new directory fails. Any ideas what could be wrong? Any

[GENERAL] OT: looking for open source developers in ukraine, or Georgia Russia

2005-02-24 Thread Dave Cramer
First of all apologies for the noise. Please reply off list. Dave -- Dave Cramer http://www.postgresintl.com 519 939 0336 ICQ#14675561 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Simon Riggs
On Wed, 2005-02-23 at 19:31 -0500, Tom Lane wrote: Ron Mayer [EMAIL PROTECTED] writes: +if (needed MaxFSMPages) +ereport(WARNING, +(errmsg(max_fsm_pages(%d) is smaller than total pages needed(%.0f), + MaxFSMPages, needed))); An unconditional

Re: [GENERAL] Report of some problem under PL/PGSQL 7.4.7 8.0.1

2005-02-24 Thread Stephan Szabo
On Thu, 24 Feb 2005, Froggy / Froggy Corp. wrote: tetris=# select test_array(); NOTICE: 17 NOTICE: 33 ERROR: invalid array subscripts CONTEXT: PL/pgSQL function test_array line 16 at assignment To correct this error message, i need to make 2 init, the

[GENERAL] Postgre 8.0 vs 7.3

2005-02-24 Thread Charl Gerber
Hi, We have a production environment running postgre 7.3.4 under linux. We are thinking about setting up a windows only development environment, which would mean we have to run postgre 8.0 on a windows machine. Question is, will the code developed under 8.0 run without problems under 7.3.4?

Re: [GENERAL] Help with tools...

2005-02-24 Thread Cristian Prieto
Something like pgAdmin III but more oriented to use as a SP editor, something like pl/sql developer (http://www.allroundautomations.com/plsqldev.html) Is something similar out there? - Original Message - From: Jason Earl [EMAIL PROTECTED] To: Cristian Prieto [EMAIL PROTECTED] Cc:

Re: [GENERAL] maximum size

2005-02-24 Thread Sven Willenberger
On Wed, 2005-02-23 at 15:34 +0100, Molinet Sylviane wrote: Hello, could you be so kind to help me with following requests ? I need the maximum size of the following types : varchar(n) numeric(n,p) text bytea Could you please give me the name of articles or publications and where I

[GENERAL] PGS 7.4.x PREPARE statement

2005-02-24 Thread Geoffrey KRETZ
Hi, I was wondering when a PREPARE statement is check. (ie : is it normal that the following statement doesn't return an error : PREPARE stmnt AS ) ? Geoffrey Kretz Four J's Development Tools ---(end of broadcast)--- TIP 9: the

Re: [GENERAL] Fedora postgresql not starting

2005-02-24 Thread Tom Lane
Ulrich Wisser [EMAIL PROTECTED] writes: I installed the latest postgresql packages on my Fedora Core 3 box. PG will not start, even initdb on a new directory fails. Any ideas what could be wrong? Any ideas how to debug? Define latest --- an exact RPM version number would be useful. We've

Re: [GENERAL] PGS 7.4.x PREPARE statement

2005-02-24 Thread Tom Lane
Geoffrey KRETZ [EMAIL PROTECTED] writes: I was wondering when a PREPARE statement is check. (ie : is it normal that the following statement doesn't return an error : PREPARE stmnt AS ) ? Hm? regression=# PREPARE stmnt AS ; ERROR: syntax error at or near

Re: [GENERAL] maximum size

2005-02-24 Thread Scott Marlowe
On Wed, 2005-02-23 at 08:34, Molinet Sylviane wrote: Hello, could you be so kind to help me with following requests ? I need the maximum size of the following types : varchar(n) ~ 1 Meg numeric(n,p) no limit (actually ~ 1 Gig) text ~ 1 Gig bytea ~ 1 Gig Could you please give me

Re: [GENERAL] PGS 7.4.x PREPARE statement

2005-02-24 Thread Geoffrey KRETZ
Tom Lane wrote: Geoffrey KRETZ [EMAIL PROTECTED] writes: I was wondering when a PREPARE statement is check. (ie : is it normal that the following statement doesn't return an error : PREPARE stmnt AS ) ? Hm? regression=# PREPARE stmnt AS ; ERROR: syntax

Re: [GENERAL] stats collector appears to be dying

2005-02-24 Thread Shelby Cain
--- Magnus Hagander [EMAIL PROTECTED] wrote: This is a known problem on WIndows. THe stats processor sometimes falls down under heavly load. And if you enable row-level-stats the load goes up considerably - especially during bulk inserts. //Magnus Well then I guess I'll be leaving

[GENERAL] Questions regarding notify processing.

2005-02-24 Thread Terry Lee Tucker
Hello List: I am working on the proper method for Notification processing. The application interface is X-Windows and I am using the database socket as an alternate input source to the X-Server. I have a callback that fires when there is data to read on the socket. Here is the setup: /* This

[GENERAL] Unicode support problem

2005-02-24 Thread Jatinder Sangha
Hi all, I'm having a problem with unicode support in postgres under linux. The issue is that I am copying lots of data from an MS SQL Server database via java/jdbc running on Windows XP over to a postgres database running on linux. I've setup the postgres database as follows: LANG=C initdb -E

[GENERAL] Unsuscribe

2005-02-24 Thread Alexis Vasquez
__ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please

Re: [GENERAL] Questions regarding notify processing.

2005-02-24 Thread Tom Lane
Terry Lee Tucker [EMAIL PROTECTED] writes: All this works great except for certain cases where one of the notify messages, the one I'm really interested in, gets spooled, queued, or something and is not delivered until I send another notification, after the fact, from another client; then,

Re: [GENERAL] Unicode support problem

2005-02-24 Thread Tom Lane
Jatinder Sangha [EMAIL PROTECTED] writes: I've setup the postgres database as follows: LANG=C initdb -E UNICODE createdb -E UNICODE I have tried setting locale/lc_ctype to C, POSIX, iso_8859_1, all kinds of things, and nothing seems to fix it. You can't just pick random combinations of

Re: [GENERAL] Questions regarding notify processing.

2005-02-24 Thread Terry Lee Tucker
Thanks for the reply Tom. See comments below: On Thursday 24 February 2005 12:06 pm, Tom Lane saith: Terry Lee Tucker [EMAIL PROTECTED] writes: All this works great except for certain cases where one of the notify messages, the one I'm really interested in, gets spooled, queued, or

[GENERAL] update queries taking lot of time

2005-02-24 Thread vinita bansal
Hi, I am running update query of the form update tablename set x = y where exists (select .) These queries are taking lots of time. I dropped all indices on the table which provided some improvement but not remarkable performance. I am looking for ways to improve it. Can someone suggest

Re: [GENERAL] update queries taking lot of time

2005-02-24 Thread Dann Corbit
Give the schema of your table. Give the exact query/queries you are running. Give the cardinality of the table. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of vinita bansal Sent: Thursday, February 24, 2005 10:21 AM To: pgsql-general@postgresql.org

Re: [GENERAL] ADO and timestamp/date errors

2005-02-24 Thread Craig Bryden
Hi Jonel In our project, we have some Visual C++ Applications that will also talk to0 the database. We are trying to stick to common drivers. The VC++ clients are having the same problem as I am reporting. Thanks Craig - Original Message - From: Jonel Rienton [EMAIL PROTECTED] To:

Re: [GENERAL] Postgre 8.0 vs 7.3

2005-02-24 Thread Jeff Davis
Well, if you're using a feature that's new in 8.0 or new in 7.4, it certainly won't work on 7.3. Aside from that, you should be OK. Look at the changelogs for details though, as 7.3 is a couple releases behind. For development, however, you normally want the same versions in the development

Re: [GENERAL] Postgre 8.0 vs 7.3

2005-02-24 Thread Scott Marlowe
On Thu, 2005-02-24 at 07:56, Charl Gerber wrote: Hi, We have a production environment running postgre 7.3.4 under linux. We are thinking about setting up a windows only development environment, which would mean we have to run postgre 8.0 on a windows machine. Question is, will the code

[GENERAL] Unsuscribe

2005-02-24 Thread Alexis Vasquez
unsuscribe __ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

[GENERAL] Help with queries...

2005-02-24 Thread Cristian Prieto
Why do I need to add "" to a table when doing a query? I've checked the examples and I found no one has " around the table names. It is something with the configuration? If I do: select * from users; ERROR: relation "users" does not exist but: select * from "Users"; returns all the data I

Re: [GENERAL] Help with queries...

2005-02-24 Thread Joshua D. Drake
Cristian Prieto wrote: Why do I need to add to a table when doing a query? I've checked the examples and I found no one has around the table names. It is something with the configuration? If I do: select * from users; ERROR: relation users does not exist but: select * from Users; returns

Re: [GENERAL] Help with queries...

2005-02-24 Thread Michael Fuhr
On Thu, Feb 24, 2005 at 02:33:28PM -0600, Cristian Prieto wrote: select * from users; ERROR: relation users does not exist but: select * from Users; returns all the data I want... See Identifiers and Keywords in the SQL Syntax chapter of the documentation, especially the parts that talk

Re: [GENERAL] Help with queries...

2005-02-24 Thread Cristian Prieto
The book says: There is a second kind of identifier: the delimited identifier or quoted identifier. It is formed by enclosing an arbitrary sequence of characters in double-quotes (). A delimited identifier is always an identifier, never a key word. So select could be used to refer to a column

[GENERAL] Newbie: help with FUNCTION

2005-02-24 Thread Charl Gerber
I'm trying to create a function that takes 1 paramater (eg an integer) as input, then does 5 database updates or deletes in 5 different SQL statements and returns 5 integers (in one resultset) indicating how many rows were affected by the various updates/deletes. How do I do this? How can I

Re: [GENERAL] Help with queries...

2005-02-24 Thread Joshua D. Drake
But my table name Grupos is not a reserved keyword, so SELECT * FROM Grupos; should work, right??? but guess what... It doesn't work too... I need to pass SELECT * FROM Grupos; That is correct. Because you have a capital letter in the table name. Sincerely, Joshua D. Drake - Original

Re: [GENERAL] Pg 8.01 big trouble with LIMIT (bug !?)

2005-02-24 Thread Bruce Momjian
My guess is that you have not ANALYZEd the tables recently and the optimizer is making a bad choice. --- Hervé Piedvache wrote: Hi, I have a simple request without a limit giving me this : # select a.id_my from

[GENERAL] basic trigger using OLD not working?

2005-02-24 Thread Rick Casey
Hello all, I am trying to a simple thing: create a log history of deletes, and updates; but which I am having trouble getting to work in PG 7.4.7 (under Debian Linux 2.6.8). I have reduced my code to the following trivial case: Here is the code that creates the delete trigger: create trigger

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Ron Mayer
Thanks everyone for the feedback on my patch. Objections I've heard (both online and in email) included: * WARNING is too strong for possibly OK behavior * It's similar to checkpoints occuring too frequently... consider increasing...checkpoint_segments which is a LOG

Re: [GENERAL] basic trigger using OLD not working?

2005-02-24 Thread Rick Casey
I am going to answer my own post here since I found more info in some threads posted here. My real question now is: does the OLD variable work at all in plpgsql? If not, then some major documentation, books and many posted messages appear to be wrong! Here is what the PostgreSQL 7.4.6

Re: [GENERAL] Help with queries...

2005-02-24 Thread Tom Lane
Cristian Prieto [EMAIL PROTECTED] writes: The book says: [snip] But my table name Grupos is not a reserved keyword, so SELECT * FROM Grupos; should work, right??? but guess what... It doesn't work too... I need to pass SELECT * FROM Grupos; You didn't read far enough: Quoting an

Re: [GENERAL] basic trigger using OLD not working?

2005-02-24 Thread Tom Lane
Rick Casey [EMAIL PROTECTED] writes: Here is the code that creates the delete trigger: create trigger PEDIGREES_hist_del_trig AFTER DELETE on PEDIGREES EXECUTE PROCEDURE logPedigreesDel(); I think you forgot FOR EACH ROW. By default, the above creates a STATEMENT trigger, in which you don't

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Tom Lane
Ron Mayer [EMAIL PROTECTED] writes: Would the updated patch below address most of the concerns? I preferred Simon's idea of not trying to produce a warning for pages when we've detected relation overflow. Making it a LOG rather than WARNING does address the issue of being too much in-your-face

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Ron Mayer
On Thu, 24 Feb 2005, Tom Lane wrote: I preferred Simon's idea of not trying to produce a warning for pages when we've detected relation overflow. Sounds good. I'll make that update. Should the relation overflow be a WARNING or a LOG? It sounds like if you have that problem it's almost

[GENERAL] Problems with query in highly concurrent environment

2005-02-24 Thread Aleksei Valikov
Hi. We have a very strange problem and no idea how to solve it. We have a PROGRESSION table that stores information about various telephony events. Rows are never updated, only inserted, about 20-30 thousand rows a day. Based on this table, we need to produce certain statistics, which are

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Tom Lane
Ron Mayer [EMAIL PROTECTED] writes: Should the relation overflow be a WARNING or a LOG? It sounds like if you have that problem it's almost certainly a problem, right? I'd go for making them both LOG, I think. More consistent. regards, tom lane

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Ron Mayer
On Thu, 24 Feb 2005, Ron Mayer wrote: Should the relation overflow be a WARNING or a LOG? It sounds like if you have that problem it's almost certainly a problem, right? And while I'm at it... what's the convention for INFOs vs LOGs? The checkpoint...too frequent seemed similar, and is a LOG.

Re: [GENERAL] basic trigger using OLD not working?

2005-02-24 Thread Rick Casey
Thanks much! That met with partial success; but getting closer. The error message about OLD went away (thankfully!), but there is still no data from the OLD variable. Here is the code again: create trigger PEDIGREES_hist_del_trig AFTER DELETE on PEDIGREES FOR EACH ROW EXECUTE PROCEDURE

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Ron Mayer
On Thu, 24 Feb 2005, Tom Lane wrote: I'd go for making them both LOG, I think. More consistent. Ok, here's another try :) With a couple more questions... 1. If I read Simon's email correctly, it implied that he wanted to see the free space map message for a VACUUM even when VERBOSE is

[GENERAL] Which query is less expensive / faster?

2005-02-24 Thread Postgres Coder
Hi all, I have a couple different ways to get results out of my table structure, but I'm unsure which way is faster or less expensive to run: Option 1: Query a table of 4 million rows, on 4 indexed columns. It will return 1 row: SELECT field1, field2, field3, field4 FROM tablea WHERE field1

Re: [GENERAL] Pg 8.0rc5 to 8.0.1 update

2005-02-24 Thread Bruce Momjian
Ben Trewern wrote: Hi, Just a quick question. Do I need to do an initdb to upgrade a cluster from v8.0rc5 to v8.0.1 or can I just do a make install. Uh, from that RC, no, I don't think so, but not all RC releases can do that, and we don't track when we require initdb during RC, so yea I

Re: [GENERAL] Porting Postgres on VXworks+SH4

2005-02-24 Thread Bruce Momjian
[EMAIL PROTECTED] wrote: Hi! I'm considering the possibility of using postgres in embededded environment with VxWorks (RTOS) Hitachi SH4 processor. Can anyone tell me if porting postgres to such a platform is possible? If yes, which version of postgres supports this? You

Re: [GENERAL] basic trigger using OLD not working?

2005-02-24 Thread Guy Rouillier
Title: Message The RAISE statement requires a % marker for each variable you want to include in the output text. --Guy Rouillier -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rick CaseySent: Thursday, February 24, 2005 5:51 PMTo:

Re: [GENERAL] Pg 8.0rc5 to 8.0.1 update

2005-02-24 Thread Tom Lane
Bruce Momjian pgman@candle.pha.pa.us writes: Just a quick question. Do I need to do an initdb to upgrade a cluster from v8.0rc5 to v8.0.1 or can I just do a make install. Uh, from that RC, no, I don't think so, but not all RC releases can do that, and we don't track when we require initdb

Re: [GENERAL] Problems with query in highly concurrent environment

2005-02-24 Thread Jim Wilson
From: Aleksei Valikov snip Moreover, what I find very strange is that when I log in with psql (or any other SQL client) onto the production database and execute the same query, it runs fast - even in peak hours! snip That is strange. Is this a networking issue? Are your clients

Re: [GENERAL] Possible to run the server with ANSI/ISO string escapeing

2005-02-24 Thread Bruce Momjian
Ken Johanson wrote: Greetings, Does anyone know if it will be possible to run the server with ANSI/ISO string escaping instead of C-style escapes? The C style escaping is a shoot-down for our adoption of postgres, since its non-standard. Not yet, but we have a TODO item: * Allow

Re: [GENERAL] Unicode support problem

2005-02-24 Thread Tatsuo Ishii
If I setup the database as follows: LANG=C initdb -E iso8859_1 createdb -E iso8859_1 Then it appears to work OK - but I then get an error with character 0xE2 (Latin small letter a with circumflex): ERROR: could not convert UTF-8 character 0x00e2 to ISO8859-1 The error message says all.

Re: [GENERAL] Which query is less expensive / faster?

2005-02-24 Thread Tzahi Fadida
I am not an expert to postgres internals but in General: if you have a btree multicolumn index on the 4 fields then it should take around logF(4M). lets guess the F to be 5 so its around 10 ios +1 block read. for the same thing for a hashtable its about the same or less. if you have any subset

Re: [GENERAL] Which query is less expensive / faster?

2005-02-24 Thread Jon Asher
Thanks for the reply... but which query will be faster and less expensive? I don't have a table now with 4 million rows, but I'm thinking of building such a table. Querying it would return 1 row. The alternative is to query an existing table of 200k rows, and return 800 rows. Option 1: Query a

Re: [GENERAL] function body error checking issues

2005-02-24 Thread Bruce Momjian
[EMAIL PROTECTED] wrote: Bruce, here is a example: (there is a simple error in the function that does not get caught when running the query in 8.0) CREATE or REPLACE FUNCTION annual.get_ratio( float8, float8) RETURNS pg_catalog.float8 AS $BODY$ DECLARE execptioncount_in alias for $1;

Re: [GENERAL] [PATCHES] A way to let Vacuum warn if FSM settings are low.

2005-02-24 Thread Bruce Momjian
Tom Lane wrote: Ron Mayer [EMAIL PROTECTED] writes: Should the relation overflow be a WARNING or a LOG? It sounds like if you have that problem it's almost certainly a problem, right? I'd go for making them both LOG, I think. More consistent. Can we also update this wording: INFO: