Re: [HACKERS] [GENERAL] One SQL to access two databases.
On Mon, Dec 02, 2002 at 08:56:41AM -0800, Joe Conway wrote: Karel Zak wrote: On Sat, Nov 30, 2002 at 01:11:20PM -0800, Joe Conway wrote: As I said, this is all very preliminary; comments, suggestions, requests are all welcome. Only idea/dream: what implement dblink as virtual schema. CREATE SCHEMA myschema AS DBLINK TO ... some connection options ...; SELECT * FROM myschema.tabname; This solution allows use dblink as really transparent. Yeah, something along these lines is in my long term vision, but I don't think it will happen for 7.4. I'd like one more contrib/dblink release for the code to mature, and to solidify the features and understand the common usage issues. Agree. This expect load a lot of information about remote tables to BE for correct planner executor running. BTW, do you think is possible load this information also from non-PostgreSQL servers (Oracle, DB2...)? The problem with multiple client-SQL libs in BE is only a small part of transparent DBLINK imlementetion. Hopefully for the release *after* 7.4 I'll be ready to make a proposal to integrate dblink into the backend, get it accepted, and get it implemented. If you want to (a lot) use client library in backend it will need real and better memory managemnt for FE libs -- for example same mmgr as use BE. Karel -- Karel Zak [EMAIL PROTECTED] http://home.zf.jcu.cz/~zakkr/ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)
I'm certainly interested! I am working here on Geographical Information Systems with PostgreSQL/PostGIS with the Minnesota MapServer, with a lot of regular database work thrown in. PostgreSQL has great potential for teaching databases and SQL, and when the native Windows port is ready, it will also be ideal for smaller, individual teaching projects (e.g. at home). Jan Hartmann Department of Geography University of Amsterdam [EMAIL PROTECTED] Gavin Sherry wrote: On Mon, 2 Dec 2002, Christopher Kings-Lynne wrote: I've given a talk in the 2002 honours lecture series at UWA about Postgres and some of the things it can do. All of those guys were interested. Especially since the deptartment does a lot of work in genetic algoriithms. Excellent. Can you put that talk online somewhere? Tell me when you start working on a document - I'm happy to help. Since I'm only just out of Uni, I'd like to write a set of possible assignments and learning outcomes and how you can use postgres to support them. My girlfriend is a PhD student at UWA CS dept :) plus I won the honours scholarship there a year or two back, so I can get interest from the dept, including the databases lecturer. Might help for another point of view and feedback. Excellent. Are there any other people involved in PostgreSQL and universities or educational institutions? If so we could put something together about experiences for the advocacy Web site. That's tragic. Teaching kids to admin oracle is something you do in Tafe, or an Oracle course, not a university. Anyway, what kind of course teaches you about how to admin oracle as opposed to teaching you about ACID properties, MVCC, distributed transactions and partitioning? Most of which can be demonstrated with Postgres. We learnt about relational model, algebra and calculus well before learning about SQL! Your interest in this is clearly the same as mine: Universities (should) teach concept not product. I'm disgusted that this is not the case. If other people are interested we could work on this in January when I am over your way, as discussed in private email. Gavin ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone?
-Original Message- From: mlw [mailto:[EMAIL PROTECTED]] Sent: 03 December 2002 06:17 To: psqlodbc; [EMAIL PROTECTED] Subject: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone? I am working on getting a shrink-wrapped version of PostgreSQL for Windows Currently it installs a customized version of Cygwin, PostgreSQL 7.2.3, cygipc, psqlodbc, and pgadminII I currently have the setup done. The target audience is not the enterprise, it is aimed at people using Access wanting to upgrade. I've looked long and hard and can't find any license issues. Does anyone know of any that I may have missed? As far as I can see, as long as I maintain GPL restrictions, I should be fine. No problems with pgAdmin, though I do have to wonder how you've done the installer? Regards, Dave. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] 7.4 Wishlist
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
Now convert this query so that it only evaluates the date_part thing
ONCE:
select t.id, date_part('days',now()-t.stamp) from table_name t where
date_part('days',now()-t.stamp) 20;
Something like this could work:
select *
from (select t.id, date_part('days',now()-t.stamp) AS d
from table_name t) AS t1
where t1.d 20;
That aside I also would like some sort of local names. Something like the
let construct used in many functional languages (not exaclty what you want
above, but still):
let t1 = select * from foo;
t2 = select * from bar;
in select * from t1 natural join t2;
But even though I would like to give name to subexpressions like above, I
still think postgresql should stick to standards as close as possible.
--
/Dennis
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 Wishlist
On Mon, Dec 02, 2002 at 12:48:38PM -0800, Christopher Kings-Lynne wrote: But if there is, then the sum/count(*) is nonsensical anyway. You must to use it in SERIALIZABLE transaction isolation. Karel -- Karel Zak [EMAIL PROTECTED] http://home.zf.jcu.cz/~zakkr/ ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone?
I've looked long and hard and can't find any license issues. Does anyone know of any that I may have missed? As far as I can see, as long as I maintain GPL restrictions, I should be fine. PostgreSQL isn't licensed under the GPL, so it sounds to me as though you're confused about the licensing issues. -- (concatenate 'string cbbrowne @cbbrowne.com) http://www3.sympatico.ca/cbbrowne/lsf.html My mom said she learned how to swim. Someone took her out in the lake and threw her off the boat. That's how she learned how to swim. I said, 'Mom, they weren't trying to teach you how to swim.' -- Paula Poundstone ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone?
[EMAIL PROTECTED] wrote: I've looked long and hard and can't find any license issues. Does anyone know of any that I may have missed? As far as I can see, as long as I maintain GPL restrictions, I should be fine. PostgreSQL isn't licensed under the GPL, so it sounds to me as though you're confused about the licensing issues. I'm not confused about the licensing issues. PostgreSQL is less restrictive than is GPL. Maybe I should have phrased it as the most restrictive license is GPL, so as long as I maintain GPL restrictions I should be fine. -- (concatenate 'string cbbrowne @cbbrowne.com) http://www3.sympatico.ca/cbbrowne/lsf.html My mom said she learned how to swim. Someone took her out in the lake and threw her off the boat. That's how she learned how to swim. I said, 'Mom, they weren't trying to teach you how to swim.' -- Paula Poundstone ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 Wishlist
On Tue, 2002-12-03 at 09:20, Dennis Björklund wrote:
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
Now convert this query so that it only evaluates the date_part thing
ONCE:
select t.id, date_part('days',now()-t.stamp) from table_name t where
date_part('days',now()-t.stamp) 20;
Something like this could work:
select *
from (select t.id, date_part('days',now()-t.stamp) AS d
from table_name t) AS t1
where t1.d 20;
That aside I also would like some sort of local names. Something like the
let construct used in many functional languages (not exaclty what you want
above, but still):
let t1 = select * from foo;
t2 = select * from bar;
in select * from t1 natural join t2;
But even though I would like to give name to subexpressions like above, I
still think postgresql should stick to standards as close as possible.
the standard way of doing it would be SQL99's WITH :
with t1 as (select * from foo)
t2 as (select * from bar)
select * from t1 natural join t2;
you can even use preceeding queries
with t1 as (select a,b from foo)
t1less as (select a,b from t1 where a 0)
t1zero as (select a,b from t1 where a = 0)
select * from t1zero, t1less, where t1zero.b = t1less.a;
Having working WITH clause is also a prerequisite to implementing SQL99
recursive queries (where each query in WITH clause sees all other
queries in the WITH clause)
I sent a patch to this list recently that implements the above syntax,
but I currently dont have knowledge (nor time to aquire it), so if
someone else does not do it it will have to wait until January.
OTOH, I think that turning my parsetree to a plan would be quite easy
for someone familiar with turning parestrees into plans ;)
I offer to check if it works in current (and make it work again if it
does not) if someone would be willing to hold my hand in implementation
parsetree--plan part ;).
I think that for non-recursive queries this is all that needs to be
done, i.e. the plan would not care if the subqueries were from FROM,
from WITH or from separately defined views.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [HACKERS] 7.4 Wishlist
On 3 Dec 2002, Hannu Krosing wrote: the standard way of doing it would be SQL99's WITH : Great! I havn't looked too much at sql99 yet so I've missed this. It's exactly what I want. Now I know what I will use in the future (when it's all implemented). -- /Dennis ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] [GENERAL] 7.3 - pg_atoi: zero-length string
Was it necessary? No idea, you're welcome to search through the
pgsql-hackers archives to determine the reasoning behind the change. I
believe the change was made by Bruce Momjian (going by the release
notes). I only remember reading the discussion in passing.
This is also one of the reasons for beta releases - to allow people to
test against the new version and pick up these sort of things. Either
this gives them/you time to make changes, or to lobby to get the old
behaviour back.
If I were in your situation i'd probably hack back the old behaviour
to 7.3, compile and run that while changes were made. Or stick with
7.2.x until changes were made to your applications, have you got a
'big carrot' for going with 7.3?
Lee.
Ben-Nes Michael writes:
That's indeed very nice but I don't see the logic in it.
If I want to upgrade I need to go on all my projects and change thousands of
lines.
And that's not all :(
I have other applications like phprojekt that was not developed by me and
became useless now as I cant insert.
Was this step so necessary ?
- Original Message -
From: Lee Kindness [EMAIL PROTECTED]
To: Ben-Nes Michael [EMAIL PROTECTED]
Cc: postgresql [EMAIL PROTECTED]; Lee Kindness
[EMAIL PROTECTED]
Sent: Tuesday, December 03, 2002 12:37 PM
Subject: [GENERAL] 7.3 - pg_atoi: zero-length string
Hi, one of the changes in 7.3 was to disallow '' being implicitly
converted to 0. In your example below image_order is clearly not a
text/char column, so what are you trying to set it too? If you want it
be 0 then explicitly use 0, if you want it to be undefined then use
NULL.
Lee.
Ben-Nes Michael writes:
Hi
After I upgraded 7.2.3 to 7.3 I started to get the following errors:
pg_atoi: zero-length string
its seems that i get it when not all field have content:
this is one example that generate the error:
insert into images (section_id, pic_date, image_order) values ('8',
'2002-12-03', '')
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 03 December 2002 12:16 To: [EMAIL PROTECTED] Subject: Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone? I've looked long and hard and can't find any license issues. Does anyone know of any that I may have missed? As far as I can see, as long as I maintain GPL restrictions, I should be fine. PostgreSQL isn't licensed under the GPL, so it sounds to me as though you're confused about the licensing issues. No, I don't think he is - Cygwin is GPL and psqlODBC is LGPL. Regards, Dave. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone?
Dave Page wrote: -Original Message- From: mlw [mailto:[EMAIL PROTECTED]] Sent: 03 December 2002 06:17 To: psqlodbc; [EMAIL PROTECTED] Subject: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone? I am working on getting a shrink-wrapped version of PostgreSQL for Windows Currently it installs a customized version of Cygwin, PostgreSQL 7.2.3, cygipc, psqlodbc, and pgadminII I currently have the setup done. The target audience is not the enterprise, it is aimed at people using Access wanting to upgrade. I've looked long and hard and can't find any license issues. Does anyone know of any that I may have missed? As far as I can see, as long as I maintain GPL restrictions, I should be fine. No problems with pgAdmin, though I do have to wonder how you've done the installer? Regards, Dave. Brute force, of course! Seriously, I have hidden the cygwin environment and simply called it PostgreSQL. I am managing all he environment variables in my installer, and I am using Windows batch files to start bash which executes the PostgreSQL comands. I am using PGAdmin as the administration tool It really looks slick ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone?
-Original Message- From: mlw [mailto:[EMAIL PROTECTED]] Sent: 03 December 2002 12:44 To: Dave Page Cc: psqlodbc; [EMAIL PROTECTED] Subject: Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone? Dave Page wrote: No problems with pgAdmin, though I do have to wonder how you've done the installer? Regards, Dave. Brute force, of course! Seriously, I have hidden the cygwin environment and simply called it PostgreSQL. I am managing all he environment variables in my installer, and I am using Windows batch files to start bash which executes the PostgreSQL comands. I am using PGAdmin as the administration tool It really looks slick I was thinking more about how you've dealt with installing pgAdmin, or have you left it seperate? If you need any help with that side of it, just let me know... Sounds good though... Regards, Dave (aka [EMAIL PROTECTED]). ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] Backend crash with tsearch
I'm evaluating tsearch contrib module, and i get a backend crash when i'm about to use a tsearch function. When i issue update things set nidx=txt2txtidx(productname), didx=txt2txtidx(longdescription); The backend dies in a segfault. The system is redhat 7.3 dual athlon w/ 1GB memory. Postgresql is compiled with -march=athlon -O3. initdb -E LATIN1 I have a huge shared buffer count (65536). I'll reinstall tsearch and try again soon. Is it necesary to install OpenFTS contrib aswell, or do i get away with only installing tsearch? Now i do both... Backtrace: #0 0x02d1 in ?? () #1 0x401faf48 in ?? () #2 0x401fb5e6 in ?? () #3 0x080d8f5c in ExecMakeFunctionResult (fcache=0x82d3710, arguments=0x82ce170, econtext=0x82d3580, isNull=0xbfffec8f , isDone=0xbfffecd8) at execQual.c:839 #4 0x080d99a3 in ExecEvalExpr (expression=0x82ce188, econtext=0x82d3580, isNull=0xbfffec8f , isDone=0xbfffecd8) at execQual.c:1168 #5 0x080d9d44 in ExecTargetList (targetlist=0x82ce3d8, nodomains=21, targettype=0x82cf230, values=0x82d4488, econtext=0x82d3580, isDone=0xbfffee78) at execQual.c:2058 #6 0x080da13f in ExecProject (projInfo=0x82d3b08, isDone=0xbfffee78) at execQual.c:2282 #7 0x080da229 in ExecScan (node=0x82cfeb8, accessMtd=0x80e1270 SeqNext) at execScan.c:133 #8 0x080e1093 in ExecSeqScan (node=0x82cfeb8) at nodeSeqscan.c:133 #9 0x080d7d9c in ExecProcNode (node=0x82cfeb8, parent=0x0) at execProcnode.c:291 #10 0x080d6a47 in ExecutePlan (estate=0x82d, plan=0x82cfeb8, operation=CMD_UPDATE, numberTuples=0, direction=ForwardScanDirection, destfunc=0x82d3b30) at execMain.c:954 #11 0x080d7682 in ExecutorRun (queryDesc=0x82d35f0, estate=0x82d, direction=ForwardScanDirection, count=0) at execMain.c:195 #12 0x0812a8cb in ProcessQuery (parsetree=0x82cb1c8, plan=0x82cfeb8, dest=Remote, completionTag=0xb060 ) at pquery.c:242 #13 0x08128b81 in pg_exec_query_string (query_string=0x82cb0a8, dest=Remote, parse_context=0x8291cd0) at postgres.c:838 #14 0x08129b50 in PostgresMain (argc=4, argv=0xb2e0, username=0x827ccd1 mag) at postgres.c:2016 #15 0x0810f0c4 in DoBackend (port=0x827cba0) at postmaster.c:2293 #16 0x0810e9dc in BackendStartup (port=0x827cba0) at postmaster.c:1915 #17 0x0810de8d in ServerLoop () at postmaster.c:1000 #18 0x0810da24 in PostmasterMain (argc=1, argv=0x8245640) at postmaster.c:779 #19 0x080ea5c2 in main (argc=1, argv=0xbc74) at main.c:210 #20 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 Magnus -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Programmer/Networker [|] Magnus Naeslund -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] Planned small change in EXPLAIN behavior
I am thinking of tweaking EXPLAIN so that it performs ExecutorStart() and ExecutorEnd() even when you just do plain EXPLAIN (and not EXPLAIN ANALYZE). The immediate reason for this is an internal change (details below) but it would have a couple of user-visible side effects: 1. Permissions checking would occur on the tables referenced in the query. Right now it's possible for a user to EXPLAIN a query he would not be allowed to execute, which seems like a bad idea. (For example, a person could infer something about the statistics of a table he couldn't read, such as column min or max values, by seeing how the planner optimizes different queries.) 2. Appropriate locks would be acquired on the tables. This is probably not an improvement, but I don't think it's unpleasant enough to be worth worrying about. Any thoughts or objections? regards, tom lane (BTW, the REAL reason I want to do this: as part of the read-only-plans project I would like to get rid of the planner's present activity of building lists of SubPlans. They're a pain in the neck to maintain and aren't useful to the planner itself. The executor can easily build the lists as part of the PlanState tree during ExecutorStart, since it'll be groveling over the whole plan tree anyway. The *only* place in the system that needs this info outside the executor is EXPLAIN --- which does ExecutorStart anyway if it's the EXPLAIN ANALYZE case. Rather than writing a bunch of extra code to find the subplans the hard way, I want to just call ExecutorStart always.) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Backend crash with tsearch
Magnus Naeslund(f) [EMAIL PROTECTED] writes: The backend dies in a segfault. Backtrace: #0 0x02d1 in ?? () #1 0x401faf48 in ?? () #2 0x401fb5e6 in ?? () #3 0x080d8f5c in ExecMakeFunctionResult (fcache=0x82d3710, arguments=0x82ce170, econtext=0x82d3580, isNull=0xbfffec8f , isDone=0xbfffecd8) at execQual.c:839 Did you compile tsearch with debug support? If so, the lack of any symbolic info here must mean that gdb didn't know where to find the tsearch .so module. You could get a more useful trace by telling gdb sharedlibrary /path/to/tsearch.so regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Backend crash with tsearch
Tom Lane [EMAIL PROTECTED] wrote: Magnus Naeslund(f) [EMAIL PROTECTED] writes: The backend dies in a segfault. Backtrace: #0 0x02d1 in ?? () #1 0x401faf48 in ?? () #2 0x401fb5e6 in ?? () #3 0x080d8f5c in ExecMakeFunctionResult (fcache=0x82d3710, arguments=0x82ce170, econtext=0x82d3580, isNull=0xbfffec8f , isDone=0xbfffecd8) at execQual.c:839 Did you compile tsearch with debug support? If so, the lack of any symbolic info here must mean that gdb didn't know where to find the tsearch .so module. You could get a more useful trace by telling gdb sharedlibrary /path/to/tsearch.so regards, tom lane I'm working on it (--enable-debug --enable-cassert). It's either that it can't load the lib (shouldn't it complain?) or it's a bad pointer. We'll find out, i hope... Magnus ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Backend crash with tsearch
Magnus Naeslund\(f\) [EMAIL PROTECTED] writes: It's either that it can't load the lib (shouldn't it complain?) or it's a bad pointer. Be sure to eliminate the possibility that you're loading the wrong version of the .so (ie, loading a 7.2 tsearch.so into 7.3). People get bit by that quite frequently right after an upgrade ... regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Backend crash with tsearch
More info, the gdb sharedlibrary loaded some more symbols: (gdb) bt #0 0x02d1 in ?? () #1 0x401faf48 in parsetext (prs=0xbfffea60, buf=0x4277eb3c Can - Live 1971-77, buflen=18) at txtidx.c:366 #2 0x401fb5e6 in txt2txtidx (fcinfo=0xbfffeaf0) at txtidx.c:487 #3 0x080ec45c in ExecMakeFunctionResult (fcache=0x83172bc, arguments=0x831187c, econtext=0x8317114, isNull=0xbfffec8f , isDone=0xbfffecd8) at execQual.c:839 #4 0x080ed023 in ExecEvalExpr (expression=0x8311898, econtext=0x8317114, isNull=0xbfffec8f , isDone=0xbfffecd8) at execQual.c:1168 #5 0x080ed3c4 in ExecTargetList (targetlist=0x8311b20, nodomains=21, targettype=0x8312b1c, values=0x83180a0, econtext=0x8317114, isDone=0xbfffee78) at execQual.c:2058 #6 0x080ed7bf in ExecProject (projInfo=0x8317f90, isDone=0xbfffee78) at execQual.c:2282 #7 0x080ed8a9 in ExecScan (node=0x8315e60, accessMtd=0x80f4fa0 SeqNext) at execScan.c:133 #8 0x080f4e73 in ExecSeqScan (node=0x8315e60) at nodeSeqscan.c:133 #9 0x080eafbc in ExecProcNode (node=0x8315e60, parent=0x0) at execProcnode.c:291 #10 0x080e99f7 in ExecutePlan (estate=0x83161ac, plan=0x8315e60, operation=CMD_UPDATE, numberTuples=0, direction=ForwardScanDirection, destfunc=0x8317fbc) at execMain.c:954 #11 0x080ea999 in ExecutorRun (queryDesc=0x831718c, estate=0x83161ac, direction=ForwardScanDirection, count=0) at execMain.c:195 #12 0x08143b9b in ProcessQuery (parsetree=0x830c8c4, plan=0x8315e60, dest=Remote, completionTag=0xb060 ) at pquery.c:242 #13 0x08141dc1 in pg_exec_query_string (query_string=0x830c79c, dest=Remote, parse_context=0x82d6e88) at postgres.c:838 #14 0x08142e1d in PostgresMain (argc=4, argv=0xb2e0, username=0x82c23a9 mag) at postgres.c:2016 #15 0x08125544 in DoBackend (port=0x82c2278) at postmaster.c:2293 #16 0x08124e5c in BackendStartup (port=0x82c2278) at postmaster.c:1915 #17 0x0812430d in ServerLoop () at postmaster.c:1000 #18 0x08123e94 in PostmasterMain (argc=1, argv=0x8276d00) at postmaster.c:779 #19 0x080fefe2 in main (argc=1, argv=0xbc74) at main.c:210 #20 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 Magnus ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] ALTER TABLE schema SCHEMA TO new_schema?
Rod Taylor wrote: Why just restrict them to moving tables? What if someone wants to move a function or an aggregate to another schema? What if they want to copy it? Copying might be tricky, but I'd be happy to help with moving everything else around. Though I don't think sequences can move (until we can properly track their dependencies) but everything else should be able to. Copy is another story all together. But I'd like a CREATE SCHEMA ... AS COPY schemaname; Wouldn't it be better to use pg_dump/pg_restore for that? If we could ask for just oen/some of the non-system schemas to be dumped it would be easy to restore it as another or even move it to another database. And one could dump only the schema or schema+data, as needed. Of course, dependencies would have to be handled as objects can refer to objects in other schemas. -- Fernando Nasser Red Hat Canada Ltd. E-Mail: [EMAIL PROTECTED] 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Backend crash with tsearch
Does it crashed?
# select txt2txtidx('Can - Live 1971-77');
Line txtidx.c:366 :
lemm = lemmatize(token, lenlemm, type);
lemmatize() is defined in morph.c. Did you use another modules for postgresql?
It seems to me that we see a name conflict. Function lemmatize is defined in
somewhere also.
Magnus Naeslund(f) wrote:
More info, the gdb sharedlibrary loaded some more symbols:
(gdb) bt
#0 0x02d1 in ?? ()
#1 0x401faf48 in parsetext (prs=0xbfffea60, buf=0x4277eb3c Can - Live
1971-77, buflen=18) at txtidx.c:366
#2 0x401fb5e6 in txt2txtidx (fcinfo=0xbfffeaf0) at txtidx.c:487
#3 0x080ec45c in ExecMakeFunctionResult (fcache=0x83172bc,
arguments=0x831187c, econtext=0x8317114, isNull=0xbfffec8f ,
isDone=0xbfffecd8) at execQual.c:839
#4 0x080ed023 in ExecEvalExpr (expression=0x8311898,
econtext=0x8317114, isNull=0xbfffec8f , isDone=0xbfffecd8)
at execQual.c:1168
#5 0x080ed3c4 in ExecTargetList (targetlist=0x8311b20, nodomains=21,
targettype=0x8312b1c, values=0x83180a0,
econtext=0x8317114, isDone=0xbfffee78) at execQual.c:2058
#6 0x080ed7bf in ExecProject (projInfo=0x8317f90, isDone=0xbfffee78) at
execQual.c:2282
#7 0x080ed8a9 in ExecScan (node=0x8315e60, accessMtd=0x80f4fa0
SeqNext) at execScan.c:133
#8 0x080f4e73 in ExecSeqScan (node=0x8315e60) at nodeSeqscan.c:133
#9 0x080eafbc in ExecProcNode (node=0x8315e60, parent=0x0) at
execProcnode.c:291
#10 0x080e99f7 in ExecutePlan (estate=0x83161ac, plan=0x8315e60,
operation=CMD_UPDATE, numberTuples=0,
direction=ForwardScanDirection, destfunc=0x8317fbc) at
execMain.c:954
#11 0x080ea999 in ExecutorRun (queryDesc=0x831718c, estate=0x83161ac,
direction=ForwardScanDirection, count=0) at execMain.c:195
#12 0x08143b9b in ProcessQuery (parsetree=0x830c8c4, plan=0x8315e60,
dest=Remote, completionTag=0xb060 ) at pquery.c:242
#13 0x08141dc1 in pg_exec_query_string (query_string=0x830c79c,
dest=Remote, parse_context=0x82d6e88) at postgres.c:838
#14 0x08142e1d in PostgresMain (argc=4, argv=0xb2e0,
username=0x82c23a9 mag) at postgres.c:2016
#15 0x08125544 in DoBackend (port=0x82c2278) at postmaster.c:2293
#16 0x08124e5c in BackendStartup (port=0x82c2278) at postmaster.c:1915
#17 0x0812430d in ServerLoop () at postmaster.c:1000
#18 0x08123e94 in PostmasterMain (argc=1, argv=0x8276d00) at
postmaster.c:779
#19 0x080fefe2 in main (argc=1, argv=0xbc74) at main.c:210
#20 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
Magnus
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Backend crash with tsearch
Teodor Sigaev wrote:
Does it crashed?
# select txt2txtidx('Can - Live 1971-77');
Line txtidx.c:366 :
lemm = lemmatize(token, lenlemm, type);
lemmatize() is defined in morph.c. Did you use another modules for
postgresql?
It seems to me that we see a name conflict. Function lemmatize is
defined in somewhere also.
Magnus Naeslund(f) wrote:
More info, the gdb sharedlibrary loaded some more symbols:
(gdb) bt
#0 0x02d1 in ?? ()
#1 0x401faf48 in parsetext (prs=0xbfffea60, buf=0x4277eb3c Can - Live
1971-77, buflen=18) at txtidx.c:366
#2 0x401fb5e6 in txt2txtidx (fcinfo=0xbfffeaf0) at txtidx.c:487
#3 0x080ec45c in ExecMakeFunctionResult (fcache=0x83172bc,
arguments=0x831187c, econtext=0x8317114, isNull=0xbfffec8f ,
isDone=0xbfffecd8) at execQual.c:839
Pointers 0x40* - functions in tsearch.so, 0x08 - postgres file.
So first string '#0 0x02d1 in ?? ()' has pointer to 'black hole'.
Very strange
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [HACKERS] Backend crash with tsearch
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote: I'm evaluating tsearch contrib module, and i get a backend crash when i'm about to use a tsearch function. When i issue update things set nidx=txt2txtidx(productname), didx=txt2txtidx(longdescription); The backend dies in a segfault. The system is redhat 7.3 dual athlon w/ 1GB memory. Postgresql is compiled with -march=athlon -O3. initdb -E LATIN1 Please, tell us postgresql version. Did you reinstall tsearch after upgrading ? Test-suite (data, sql) demonstrated the problem would be nice. I have a huge shared buffer count (65536). I'll reinstall tsearch and try again soon. Is it necesary to install OpenFTS contrib aswell, or do i get away with only installing tsearch? For contrib/tsearch you need only tsearch :) Now i do both... Backtrace: #0 0x02d1 in ?? () #1 0x401faf48 in ?? () #2 0x401fb5e6 in ?? () #3 0x080d8f5c in ExecMakeFunctionResult (fcache=0x82d3710, arguments=0x82ce170, econtext=0x82d3580, isNull=0xbfffec8f , isDone=0xbfffecd8) at execQual.c:839 #4 0x080d99a3 in ExecEvalExpr (expression=0x82ce188, econtext=0x82d3580, isNull=0xbfffec8f , isDone=0xbfffecd8) at execQual.c:1168 #5 0x080d9d44 in ExecTargetList (targetlist=0x82ce3d8, nodomains=21, targettype=0x82cf230, values=0x82d4488, econtext=0x82d3580, isDone=0xbfffee78) at execQual.c:2058 #6 0x080da13f in ExecProject (projInfo=0x82d3b08, isDone=0xbfffee78) at execQual.c:2282 #7 0x080da229 in ExecScan (node=0x82cfeb8, accessMtd=0x80e1270 SeqNext) at execScan.c:133 #8 0x080e1093 in ExecSeqScan (node=0x82cfeb8) at nodeSeqscan.c:133 #9 0x080d7d9c in ExecProcNode (node=0x82cfeb8, parent=0x0) at execProcnode.c:291 #10 0x080d6a47 in ExecutePlan (estate=0x82d, plan=0x82cfeb8, operation=CMD_UPDATE, numberTuples=0, direction=ForwardScanDirection, destfunc=0x82d3b30) at execMain.c:954 #11 0x080d7682 in ExecutorRun (queryDesc=0x82d35f0, estate=0x82d, direction=ForwardScanDirection, count=0) at execMain.c:195 #12 0x0812a8cb in ProcessQuery (parsetree=0x82cb1c8, plan=0x82cfeb8, dest=Remote, completionTag=0xb060 ) at pquery.c:242 #13 0x08128b81 in pg_exec_query_string (query_string=0x82cb0a8, dest=Remote, parse_context=0x8291cd0) at postgres.c:838 #14 0x08129b50 in PostgresMain (argc=4, argv=0xb2e0, username=0x827ccd1 mag) at postgres.c:2016 #15 0x0810f0c4 in DoBackend (port=0x827cba0) at postmaster.c:2293 #16 0x0810e9dc in BackendStartup (port=0x827cba0) at postmaster.c:1915 #17 0x0810de8d in ServerLoop () at postmaster.c:1000 #18 0x0810da24 in PostmasterMain (argc=1, argv=0x8245640) at postmaster.c:779 #19 0x080ea5c2 in main (argc=1, argv=0xbc74) at main.c:210 #20 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 Magnus -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Programmer/Networker [|] Magnus Naeslund -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] ALTER TABLE schema SCHEMA TO new_schema?
Copy is another story all together. But I'd like a CREATE SCHEMA ... AS COPY schemaname; Wouldn't it be better to use pg_dump/pg_restore for that? Perhaps.. But I'd really like to see some of these types of abilities added to pg_admin. -- Rod Taylor [EMAIL PROTECTED] PGP Key: http://www.rbt.ca/rbtpub.asc signature.asc Description: This is a digitally signed message part
Re: [HACKERS] How to compile postgres source code in VC++
On Fri, 29 Nov 2002, Prasanna Phadke wrote: Can anybody explain me, how to compile postgres source code in VC++. Catch all the cricket action. Download Yahoo! Score tracker Step 1: Get VC++ to run under unix... Just kidding. :-) Right now you can't. pgsql 7.4 should support native Windows environment. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Backend crash with tsearch
Some more (useless) info. objdump -x /lib/*.so /usr/lib/*.so /lib/i686/*.so /usr/kerberos/lib/*.so /usr/local/pgsql/bin/* /usr/local/pgsql/lib/*.so | grep lemmatize reviels only one lemmatize symbol. The offending address 0x02d1 is not mapped anywhere in the address space according to /proc/pid/maps. Nice that the coredump is 522MB ;) Magnus ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)
On Tue, 3 Dec 2002, Justin Clift wrote: Excellent. Are there any other people involved in PostgreSQL and universities or educational institutions? If so we could put something together about experiences for the advocacy Web site. Is this the kind of thing that the Techdocs Guides area would be good for? (http://techdocs.postgresql.org/guides) Seems that any discussions about experiences belongs on Advocacy, no? ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] How to compile postgres source code in VC++
On Tue, 2002-12-03 at 17:59, scott.marlowe wrote: On Fri, 29 Nov 2002, Prasanna Phadke wrote: Catch all the cricket action. Download Yahoo! Score tracker Step 1: Get VC++ to run under unix... Virtual Cricket++? I don't exactly see how this applies here. (sorry) -- vbi -- this email is protected by a digital signature: http://fortytwo.ch/gpg NOTE: keyserver bugs! get my key here: https://fortytwo.ch/gpg/92082481 signature.asc Description: This is a digitally signed message part
Re: [HACKERS] Backend crash with tsearch
Oleg Bartunov [EMAIL PROTECTED] wrote: Please, tell us postgresql version. Did you reinstall tsearch after upgrading ? Test-suite (data, sql) demonstrated the problem would be nice. pgsql 7.3, about 700mb text database with product descriptions. I'm working on isolation the behavior, the tsearch make installcheck seems to be crashing aswell. Is a psql regression tsearch.sql needed, or is that done automatically in the installcheck? For contrib/tsearch you need only tsearch :) :) I hope this is because of something silly. Magnus ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] 7.3 tag
I don't see any 7.3 tag created when we did the 7.3 release. (I do see the 7.3 branch.) Marc, can a tag be added to match the 7.3 release tree? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] numeric to text (7.3)
On Mon, 2 Dec 2002, Joel Burton wrote:
joel@joel=# select round('2.000'::numeric);
round
---
2
(1 row)
joel@joel=# select round('2.000'::numeric,2);
round
---
2.00
(1 row)
OK, but:
template1=# select round('2.001'::numeric);
round
---
2
(1 row)
template1=# select round('2.001'::numeric,2);
round
---
2.00
(1 row)
The good idea (in 7.2):
template1=# select text('2.000'::numeric);
text
--
2
(1 row)
template1=# select text('2.001'::numeric);
text
---
2.001
(1 row)
This feature is missing from 7.3..
(new round function is good idea (e.g. fround(numeric))
-Sygma
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] numeric to text (7.3)
On Mon, 2 Dec 2002, Rod Taylor wrote:
double precision | pg_catalog | round | double precision
numeric | pg_catalog | round | numeric
numeric | pg_catalog | round | numeric, integer
Looks like round still exists to me.
Rod, you don't understand me. :)
I needn't round, or the valueless zeroes too.
It's good (in older version of pSQL):
2.000::numeric - 2
2.001::numeric - 2.001
It's ugly (in 7.3):
2.000::numeric - 2.000
2.001::numeric - 2.001
or
round(2.000::numeric,2) - 2.00
round(2.001::numeric,2) - 2.00
Joel had got a good idea:
joel@joel=# select rtrim(rtrim('2.000'::numeric, '0'),'.');
rtrim
---
2
(1 row)
.. but i prefer the old text(numeric) function :)
Thanks!
-Sygma
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [HACKERS] Backend crash with tsearch
I'll reinstall tsearch and try again soon. Is it necesary to install OpenFTS contrib aswell, or do i get away with only installing tsearch? Now i do both... Can you give us the compressed text? I can try it on my installation and see if there's the same problem? Chris ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)
On Tue, 3 Dec 2002, Marc G. Fournier wrote: On Tue, 3 Dec 2002, Justin Clift wrote: Excellent. Are there any other people involved in PostgreSQL and universities or educational institutions? If so we could put something together about experiences for the advocacy Web site. Is this the kind of thing that the Techdocs Guides area would be good for? (http://techdocs.postgresql.org/guides) Seems that any discussions about experiences belongs on Advocacy, no? Where have you been? The lines of distinction between all of the lists have gotten so blurred it hardly makes a difference. Vince. -- http://www.meanstreamradio.com http://www.unknown-artists.com Internet radio: It's not file sharing, it's just radio. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Backend crash with tsearch
Christopher Kings-Lynne [EMAIL PROTECTED] wrote: I'll reinstall tsearch and try again soon. Is it necesary to install OpenFTS contrib aswell, or do i get away with only installing tsearch? Now i do both... Can you give us the compressed text? I can try it on my installation and see if there's the same problem? Chris No i can't, it's not my data to give :( But it doesn't matter since if you run gmake installcheck in contrib/tsearch it will explode. A funny thing is that i installed pg7.3 on an linux intel celeron system (rh8.0) w/128 mb memory, and THERE it works! Athlon dependent? (Well maybe not, the rest of 7.3 works and passes all regressiontests) Magnus ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Backend crash with tsearch
No i can't, it's not my data to give :( OK But it doesn't matter since if you run gmake installcheck in contrib/tsearch it will explode. A funny thing is that i installed pg7.3 on an linux intel celeron system (rh8.0) w/128 mb memory, and THERE it works! Works on FreeBSD/Alpha for me. Maybe you've got some weirdness with bad RAM chips or something? Chris ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Backend crash with tsearch
Christopher Kings-Lynne [EMAIL PROTECTED] wrote: Works on FreeBSD/Alpha for me. Maybe you've got some weirdness with bad RAM chips or something? Chris Could be, but it only shows when i do this, and the server has been up for several months. If everything else failes, i'll run memtest86 on it. Magnus ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)
On Tue, 3 Dec 2002, Vince Vielhaber wrote: On Tue, 3 Dec 2002, Marc G. Fournier wrote: On Tue, 3 Dec 2002, Justin Clift wrote: Excellent. Are there any other people involved in PostgreSQL and universities or educational institutions? If so we could put something together about experiences for the advocacy Web site. Is this the kind of thing that the Techdocs Guides area would be good for? (http://techdocs.postgresql.org/guides) Seems that any discussions about experiences belongs on Advocacy, no? Where have you been? The lines of distinction between all of the lists have gotten so blurred it hardly makes a difference. Actually, there are lines, Justin just occasionally appears to 'blur' them until I get a chance to refresh them ... eh Justin?:) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.4 Wishlist
Al Sutton wrote: Point to Point and Broadcast replication With point to point you specify multiple endpoints, with broadcast you can specify a subnet address and the updates are broadcast over that subnet. The difference being that point to point works well for cross network replication, or where you have a few replicants. I have multiple database servers which could have a deadicated class C network that they are all on, by broadcasting updates you can cutdown the amount of traffic on that net by a factor of n minus 1 (where n is the number of servers involved). Yech. Now you can't use TCP anymore, so the underlying replication code has to handle all the issues that TCP deals with transparently, like error checking, retransmits, data windows, etc. I don't think it's wise to assume that your transport layer is 100% reliable. Further, this doesn't even address the problem of bringing up a leaf server that's been down a while. It can be significantly out of date relative to the other servers on the subnet. I suspect you'll be better off implementing a replication protocol that has the leaf nodes keeping each other up to date, to minimize the traffic coming from the next level up. Then you can use TCP for the connections but minimize the traffic generated by any given node. Ability to use raw partitions I've not seen an install of PostgreSQL yet that didn't put the database files onto a filesystem, so I'm assuming it's the only way of doing it. By using the filesystem the files are at the mercy of filesystem handler code as to where they end up on the disk, and thus the speed of access will always have some dependancy on the speed of the filesystem. With a raw partition it would be possible to use two devices (e.g. /dev/hde and /dev/hdg on an eight channel ide linux box), and PostgreSQL could then ensure the WALs were located on one the disk with the entries running sequentally, and that the database files were located on the other disk in the most appropriate location (e.g. index data starting near the center of the disk, and user table data starting near the outside). Yeah, but now you have to worry about optimizing placement of blocks, optimizing writes, etc. These are things the OS should worry about, not the database server. If you're really that concerned about these issues, store the WAL on one (empty) filesystem and the tables on another (empty and separate) filesystem. With any reasonable filesystem you'll get reasonably close to optimal performance, especially if the filesystem code is capable of analyzing the write patterns and adapting itself accordingly. In short, I'd much rather spend the effort improving the filesystem (where everyone can benefit) than improving PostgreSQL (where only PostgreSQL users can benefit) for this item. The one good reason for making it possible to use raw partitions is to make it possible to use the PostgreSQL engine as a filesystem! :-) Win32 Port I've explained the reasons before. Apart from that it's always useful to open PostgreSQL up to a larger audience. Agreed. - Kevin Brown ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)
On 3 Dec 2002 at 15:08, Vince Vielhaber wrote: Where have you been? The lines of distinction between all of the lists have gotten so blurred it hardly makes a difference. So consider this a wake up call. -- Dan Langille : http://www.langille.org/ ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 Wishlist
Is WITH a TODO item?
---
Hannu Krosing wrote:
On Tue, 2002-12-03 at 09:20, Dennis Bj?rklund wrote:
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
Now convert this query so that it only evaluates the date_part thing
ONCE:
select t.id, date_part('days',now()-t.stamp) from table_name t where
date_part('days',now()-t.stamp) 20;
Something like this could work:
select *
from (select t.id, date_part('days',now()-t.stamp) AS d
from table_name t) AS t1
where t1.d 20;
That aside I also would like some sort of local names. Something like the
let construct used in many functional languages (not exaclty what you want
above, but still):
let t1 = select * from foo;
t2 = select * from bar;
in select * from t1 natural join t2;
But even though I would like to give name to subexpressions like above, I
still think postgresql should stick to standards as close as possible.
the standard way of doing it would be SQL99's WITH :
with t1 as (select * from foo)
t2 as (select * from bar)
select * from t1 natural join t2;
you can even use preceeding queries
with t1 as (select a,b from foo)
t1less as (select a,b from t1 where a 0)
t1zero as (select a,b from t1 where a = 0)
select * from t1zero, t1less, where t1zero.b = t1less.a;
Having working WITH clause is also a prerequisite to implementing SQL99
recursive queries (where each query in WITH clause sees all other
queries in the WITH clause)
I sent a patch to this list recently that implements the above syntax,
but I currently dont have knowledge (nor time to aquire it), so if
someone else does not do it it will have to wait until January.
OTOH, I think that turning my parsetree to a plan would be quite easy
for someone familiar with turning parestrees into plans ;)
I offer to check if it works in current (and make it work again if it
does not) if someone would be willing to hold my hand in implementation
parsetree--plan part ;).
I think that for non-recursive queries this is all that needs to be
done, i.e. the plan would not care if the subqueries were from FROM,
from WITH or from separately defined views.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Backend crash with tsearch
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote: Oleg Bartunov [EMAIL PROTECTED] wrote: Please, tell us postgresql version. Did you reinstall tsearch after upgrading ? Test-suite (data, sql) demonstrated the problem would be nice. pgsql 7.3, about 700mb text database with product descriptions. I'm working on isolation the behavior, the tsearch make installcheck seems to be crashing aswell. Is a psql regression tsearch.sql needed, or is that done automatically in the installcheck? Magnus, what is an output of 'make installcheck' ? For contrib/tsearch you need only tsearch :) :) I hope this is because of something silly. Magnus Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Wishlist for 7.4: Plan stability
Tom Lane [EMAIL PROTECTED] writes: Greg Stark [EMAIL PROTECTED] writes: Ok, someone else posted their data warehousing wishlist, I want to post my single item OLP wishlist: Plan stability. That seems to me to translate to I want the system to fail to react to changes in data statistics and all other variables relevant to query planning. You can pretty much get that by never doing [VACUUM] ANALYZE, but I'm quite lost as to why it's really a good idea. Well, first of all there's no guarantee that the genetic algorithm will actually produce the same plan twice, but that's a side issue. The main issue is that you *do* want to vacuum and analyze the database regularly to get good performance, but you don't want the database spontaneously changing its behaviour without testing and verifying the new behaviour personally. Not if it's a high availability production server. I'm thinking it should require a specific privilege that can be separately access controlled to parse a new query that didn't already exist in the query table. Then for a production server I would expect the DBA to arrange for vacuum analyze to run regularly during off-peak hours. Have a job test all the queries and report any changed optimiser behaviour. Then have a DBA sanity check and test the performance of any new query plans before allowing them to go into production. But the threat of the optimiser changing behaviour from running analyze isn't even the main threat I see this addressing. The threat of untested queries entering production from new code being pushed live is far greater. I've seen web sites go down more often from new queries with bad performance that were missed in testing more often than any other source. And I've seen security holes caused by applications that allow untrusted users to slip unexpected sql syntax into queries more often than any other reason. Really it boils down to one point: there's really no reason to assume a user should be able to execute any new query he feels like. Creating a new query should be privileged operation just like creating a new table or new database. For some systems such as development systems it of course makes sense for users to be able to create new queries on the fly. For DSS systems too it's pretty much assumed. But for OLTP systems it's very unlikely that a new query should suddenly be necessary. These systems spend their days running the same queries millions of times per day. They need to return results within milliseconds. Any new query should be assumed to be a bug or a security breach and reported as an immediate error. not cause the database to valiantly attempt to figure out how best to handle the unexpected query. -- greg ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)
Marc G. Fournier wrote: On Tue, 3 Dec 2002, Justin Clift wrote: Excellent. Are there any other people involved in PostgreSQL and universities or educational institutions? If so we could put something together about experiences for the advocacy Web site. Is this the kind of thing that the Techdocs Guides area would be good for? (http://techdocs.postgresql.org/guides) Seems that any discussions about experiences belongs on Advocacy, no? Good point. Have put a *really basic* Zwiki framework at: http://advocacy.postgresql.org/documents It's the same collaborative software used for the PostgreSQL Guides section, but without the look+feel added. If you want to start editing stuff right away, then feel free to use it. If you'd like it to look better first though, then it'll be a few days... :-) Regards and best wishes, Justin Clift -- My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there. - Indira Gandhi ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)
Marc G. Fournier wrote: snip Actually, there are lines, Justin just occasionally appears to 'blur' them until I get a chance to refresh them ... eh Justin?:) [innocent whistle] + Justin ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Backend crash with tsearch [NAILED][HELP!]
Ok, I nailed the bug, but i'm not sure what the correct fix is. Attached tsearch_morph.diff that remedies this problem by avoiding it. Also there's a debug aid patch if someone would like to know how i finally found it out :) There problem in the lemmatize() function is that GETDICT(...) returned a value not handled (BYLOCALE). The value (-1) and later used as an index into the dicts[] array. After that everything went berserk stack went crazy somehow so trapping the fault sent me to the wrong place, and every time i read the value it was positive ;) So now i just return the initial word passed to the lemmatize function, because i don't know what to do with it. So you tsearch guys will have to work it out :) Magnus tsearch_morph.c.diff Description: Binary data tsearch_morph.c.debugaid Description: Binary data ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [GENERAL] 7.3 - pg_atoi: zero-length string
The change was made to tighten up the code to catch errors sooner.
There isn't much logic to making '' be 0, and no one could make a case
for keeping such a mapping.
---
Lee Kindness wrote:
Was it necessary? No idea, you're welcome to search through the
pgsql-hackers archives to determine the reasoning behind the change. I
believe the change was made by Bruce Momjian (going by the release
notes). I only remember reading the discussion in passing.
This is also one of the reasons for beta releases - to allow people to
test against the new version and pick up these sort of things. Either
this gives them/you time to make changes, or to lobby to get the old
behaviour back.
If I were in your situation i'd probably hack back the old behaviour
to 7.3, compile and run that while changes were made. Or stick with
7.2.x until changes were made to your applications, have you got a
'big carrot' for going with 7.3?
Lee.
Ben-Nes Michael writes:
That's indeed very nice but I don't see the logic in it.
If I want to upgrade I need to go on all my projects and change thousands of
lines.
And that's not all :(
I have other applications like phprojekt that was not developed by me and
became useless now as I cant insert.
Was this step so necessary ?
- Original Message -
From: Lee Kindness [EMAIL PROTECTED]
To: Ben-Nes Michael [EMAIL PROTECTED]
Cc: postgresql [EMAIL PROTECTED]; Lee Kindness
[EMAIL PROTECTED]
Sent: Tuesday, December 03, 2002 12:37 PM
Subject: [GENERAL] 7.3 - pg_atoi: zero-length string
Hi, one of the changes in 7.3 was to disallow '' being implicitly
converted to 0. In your example below image_order is clearly not a
text/char column, so what are you trying to set it too? If you want it
be 0 then explicitly use 0, if you want it to be undefined then use
NULL.
Lee.
Ben-Nes Michael writes:
Hi
After I upgraded 7.2.3 to 7.3 I started to get the following errors:
pg_atoi: zero-length string
its seems that i get it when not all field have content:
this is one example that generate the error:
insert into images (section_id, pic_date, image_order) values ('8',
'2002-12-03', '')
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [GENERAL] 7.3 - pg_atoi: zero-length string
Hi,
| What is the solution of other dbs ( oracle, db2 .. ) to:
| insert into table (num) value (''); ? |
| I assume they would fail too.
The Oracle behaviour is:
---
oracle create table foonum (x number(5));
oracle insert into foonum values ('');
oracle select * from foonum;
+
X|
+
[NULL] |
+
---
so, '' as numeric value is regarded as NULL. But Oracle
braindeadly interprets the varchar '' as well as NULL in a varchar
column so is probably not paragon ...
IMHO, if PostgreSQL is to support an empty string for numerics at all,
then it should be interpreted as not-a-value and as such as NULL.
Interpreting it as numeric value '0' could lead to subtle bugs since this
would probably not the expected behaviour (at least not mine).
The number '0' is arbitrary, except that we happend to start counting with
it. Someone else could argue why not interpret not-a-value as '1'
(non-computer guys tend to start counting with '1') or even '42' (since
this is the answer to everything).
I personally would be prefer to raise an error on an empty string; but
interpreting it as NULL would be reasonable as well. But interpreting it
as '0' will yield many unseen programming errors and should be avoided.
my 2cent,
-hen
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [HACKERS] 7.4 Wishlist
On Tue, 2002-12-03 at 16:00, Bruce Momjian wrote:
Is WITH a TODO item?
It is disguised as
Exotic Features
===
* Add sql3 recursive unions
Which was added at my request in dark times, possibly when PostgreSQL
was called postgres95 ;)
This should be changed to two items
* Add SQL99 WITH clause to SELECT
* Add SQL99 WITH RECURSIVE to SELECT
---
Hannu Krosing wrote:
On Tue, 2002-12-03 at 09:20, Dennis Bj?rklund wrote:
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
Now convert this query so that it only evaluates the date_part thing
ONCE:
select t.id, date_part('days',now()-t.stamp) from table_name t where
date_part('days',now()-t.stamp) 20;
Something like this could work:
select *
from (select t.id, date_part('days',now()-t.stamp) AS d
from table_name t) AS t1
where t1.d 20;
That aside I also would like some sort of local names. Something like the
let construct used in many functional languages (not exaclty what you want
above, but still):
let t1 = select * from foo;
t2 = select * from bar;
in select * from t1 natural join t2;
But even though I would like to give name to subexpressions like above, I
still think postgresql should stick to standards as close as possible.
the standard way of doing it would be SQL99's WITH :
with t1 as (select * from foo)
t2 as (select * from bar)
select * from t1 natural join t2;
you can even use preceeding queries
with t1 as (select a,b from foo)
t1less as (select a,b from t1 where a 0)
t1zero as (select a,b from t1 where a = 0)
select * from t1zero, t1less, where t1zero.b = t1less.a;
Having working WITH clause is also a prerequisite to implementing SQL99
recursive queries (where each query in WITH clause sees all other
queries in the WITH clause)
I sent a patch to this list recently that implements the above syntax,
but I currently dont have knowledge (nor time to aquire it), so if
someone else does not do it it will have to wait until January.
OTOH, I think that turning my parsetree to a plan would be quite easy
for someone familiar with turning parestrees into plans ;)
I offer to check if it works in current (and make it work again if it
does not) if someone would be willing to hold my hand in implementation
parsetree--plan part ;).
I think that for non-recursive queries this is all that needs to be
done, i.e. the plan would not care if the subqueries were from FROM,
from WITH or from separately defined views.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [GENERAL] 7.3 - pg_atoi: zero-length string
If we had received more complaints about the change during beta, we
would have added a mention that the change would be in 7.4. As we got
few complaints, the change went into 7.3, and it is mentioned in the
porting section of the release notes (last item):
* An empty string ('') is no longer allowed as the input into an
integer field. Formerly, it was silently interpreted as 0.
---
Larry Rosenman wrote:
--On Tuesday, December 03, 2002 11:21:04 -0500 Bruce Momjian
[EMAIL PROTECTED] wrote:
Ben-Nes Michael wrote:
Then Why not set it to NULL
Well, it is not NULL, though, it is ''. They are not the same in
strings (though for some dbms's they are), so I don't see why we would
do that for numerics.
Seems logic as there is nothing between ''
What is the solution of other dbs ( oracle, db2 .. ) to:
insert into table (num) value (''); ?
I assume they would fail too.
Who knows how many application will suffer becouse of this.
Yours is the first, or perhaps second to bring up this issue.
I am sure it is a pain, but it does tighten up some cases where we were
silently mapping '' to 0, and we don't exactly have a flood of problem
reports.
He's at least the 2nd. I have one, that I've complained to the
PHPGroupware folks (which
BREAKS severely with this change).
LER
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania
19073
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] 7.4 Wishlist
TODO updated. Thanks for the clarification.
---
Hannu Krosing wrote:
On Tue, 2002-12-03 at 16:00, Bruce Momjian wrote:
Is WITH a TODO item?
It is disguised as
Exotic Features
===
* Add sql3 recursive unions
Which was added at my request in dark times, possibly when PostgreSQL
was called postgres95 ;)
This should be changed to two items
* Add SQL99 WITH clause to SELECT
* Add SQL99 WITH RECURSIVE to SELECT
---
Hannu Krosing wrote:
On Tue, 2002-12-03 at 09:20, Dennis Bj?rklund wrote:
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
Now convert this query so that it only evaluates the date_part thing
ONCE:
select t.id, date_part('days',now()-t.stamp) from table_name t where
date_part('days',now()-t.stamp) 20;
Something like this could work:
select *
from (select t.id, date_part('days',now()-t.stamp) AS d
from table_name t) AS t1
where t1.d 20;
That aside I also would like some sort of local names. Something like the
let construct used in many functional languages (not exaclty what you want
above, but still):
let t1 = select * from foo;
t2 = select * from bar;
in select * from t1 natural join t2;
But even though I would like to give name to subexpressions like above, I
still think postgresql should stick to standards as close as possible.
the standard way of doing it would be SQL99's WITH :
with t1 as (select * from foo)
t2 as (select * from bar)
select * from t1 natural join t2;
you can even use preceeding queries
with t1 as (select a,b from foo)
t1less as (select a,b from t1 where a 0)
t1zero as (select a,b from t1 where a = 0)
select * from t1zero, t1less, where t1zero.b = t1less.a;
Having working WITH clause is also a prerequisite to implementing SQL99
recursive queries (where each query in WITH clause sees all other
queries in the WITH clause)
I sent a patch to this list recently that implements the above syntax,
but I currently dont have knowledge (nor time to aquire it), so if
someone else does not do it it will have to wait until January.
OTOH, I think that turning my parsetree to a plan would be quite easy
for someone familiar with turning parestrees into plans ;)
I offer to check if it works in current (and make it work again if it
does not) if someone would be willing to hold my hand in implementation
parsetree--plan part ;).
I think that for non-recursive queries this is all that needs to be
done, i.e. the plan would not care if the subqueries were from FROM,
from WITH or from separately defined views.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [HACKERS] Backend crash with tsearch
As you wish... This is a bt taken from a core file this time (the other ones were from attached processes). The whole thing has been recompiled with no additional compiler flags (i.e. removed -march=athlon -O3), but still with --enable-debug and --enable-cassert. Sorry, I have no any idea. Just only full reinstall (with initdb and rm -rf /usr/local/pgsql) postgresql... Can you give me login on you computer for a several hours? -- Teodor Sigaev [EMAIL PROTECTED] ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Backend crash with tsearch
Teodor Sigaev [EMAIL PROTECTED] wrote: Sorry, I have no any idea. Just only full reinstall (with initdb and rm -rf /usr/local/pgsql) postgresql... Can you give me login on you computer for a several hours? The thing is that when i ran the thing breakpointing on parsetext() at the line of the call i could type cont many times. Could there be some kind of memory corruption, someone overwriting memory? Sorry, i can't hand out a login to the box :( I did a total re-install just now, and it still crashes. Magnus ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
On Thu, 28 Nov 2002, Bruce Momjian wrote: Wow, this sounds great. Where can I get a copy? Why would anyone use anything else? ;-) Well, if you read the announcement in its entirety, you would have noticed: Source for this release is available at: http://advocacy.postgresql.org/download/ *grin* ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
Marc G. Fournier wrote: On Thu, 28 Nov 2002, Bruce Momjian wrote: Wow, this sounds great. Where can I get a copy? Why would anyone use anything else? ;-) Well, if you read the announcement in its entirety, you would have noticed: Source for this release is available at: http://advocacy.postgresql.org/download/ Oh, good. I will go get it right now. ;-) -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: PostgreSQL in Universities (Was: Re: [HACKERS] 7.4 Wishlist)
Hi: We at the Department of Information Technology of the Mindanao State University-Iligan Institute of Technology (MSU-IIT) in Iligan City, Philippines had been using PostgreSQL since 1998 in teaching courses in Databases, SQL, and as a support tool in teaching Software Engineering and Web Application Development. We are even utilizing it as our database backend in all applications we developed in-house like Payroll, Student Enrollment, Financial Applications, etc. At the rate PostgreSQL is performing, we are not for any reason tempted to migrate to another database for the next ten years. THANKS TO THE POSTGRESQL DEVELOPMENT TEAM. We Salute YOU! PROF. MANUEL C. CABIDO Chair Department of Information Technology MSU-IIT Iligan City 9200 Philippines ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Shrinkwrap Windows Product, any issues? Anyone?
Brute force, of course! Seriously, I have hidden the cygwin environment and simply called it PostgreSQL. I am managing all he environment variables in my installer, and I am using Windows batch files to start bash which executes the PostgreSQL comands. I am using PGAdmin as the administration tool It really looks slick We've done great things at our office, using the free NullSoft installer (WinAmp): http://www.winamp.com/nsdn/nsis/ Chris ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
-Original Message- From: Marc G. Fournier [mailto:[EMAIL PROTECTED]] Sent: 03 December 2002 19:12 To: Bruce Momjian Cc: PostgreSQL-development Subject: Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces On Thu, 28 Nov 2002, Bruce Momjian wrote: Wow, this sounds great. Where can I get a copy? Why would anyone use anything else? ;-) Well, if you read the announcement in its entirety, you would have noticed: Source for this release is available at: http://advocacy.postgresql.org/download/ I could have sworn we used to have a bunch of ftp mirrors for downloads. Come to think of it I rewrote/stole a load of Vince's PHP code to allow you to select one from the portal recently. Are we not using them anymore? :-) Regards, Dave. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
On Tue, 3 Dec 2002, Dave Page wrote: -Original Message- From: Marc G. Fournier [mailto:[EMAIL PROTECTED]] Sent: 03 December 2002 19:12 To: Bruce Momjian Cc: PostgreSQL-development Subject: Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces On Thu, 28 Nov 2002, Bruce Momjian wrote: Wow, this sounds great. Where can I get a copy? Why would anyone use anything else? ;-) Well, if you read the announcement in its entirety, you would have noticed: Source for this release is available at: http://advocacy.postgresql.org/download/ I could have sworn we used to have a bunch of ftp mirrors for downloads. Come to think of it I rewrote/stole a load of Vince's PHP code to allow you to select one from the portal recently. Are we not using them anymore? Haven't you been paying attention? There's this new advocacy and suit marketing thing going on that makes all of that irrelevant. It's just there for show now. :) Vince. -- http://www.meanstreamradio.com http://www.unknown-artists.com Internet radio: It's not file sharing, it's just radio. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
On Tue, 3 Dec 2002, Dave Page wrote: I could have sworn we used to have a bunch of ftp mirrors for downloads. Come to think of it I rewrote/stole a load of Vince's PHP code to allow you to select one from the portal recently. Are we not using them anymore? Yup, as with doing anything for the firs ttime, the press release itself had its 'bugs' ... considering how many times Josh asked for comments on it, I'm surprised that nobody picked up on it *shrug* We are looking at some improvements to the download stuff ... Greg(?) suggested a layout that I really liked for a web based version that would have to tie into the main mirror database ... one that provided a wee bit more information then just the directory listings ... but, with that thought, isn't there a file you can put into an ftp directory that, when you web into that directory, i gives you the listings with various comments, or is that just using the .messages file? ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
On Tue, 3 Dec 2002, Vince Vielhaber wrote: Haven't you been paying attention? There's this new advocacy and suit marketing thing going on that makes all of that irrelevant. It's just there for show now. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Backend crash with tsearch
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote: Christopher Kings-Lynne [EMAIL PROTECTED] wrote: I'll reinstall tsearch and try again soon. Is it necesary to install OpenFTS contrib aswell, or do i get away with only installing tsearch? Now i do both... Can you give us the compressed text? I can try it on my installation and see if there's the same problem? Chris No i can't, it's not my data to give :( But it doesn't matter since if you run gmake installcheck in contrib/tsearch it will explode. A funny thing is that i installed pg7.3 on an linux intel celeron system (rh8.0) w/128 mb memory, and THERE it works! Athlon dependent? (Well maybe not, the rest of 7.3 works and passes all regressiontests) So, the problem may be in rh 7.3 ? Magnus ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Backend crash with tsearch
Oleg Bartunov [EMAIL PROTECTED] wrote:
So, the problem may be in rh 7.3 ?
Might be, i'm debugging it now, and i can see that the dicts[] array in
morph.c is beeing overwritten with junk.
I can trigger it with this query:
select txt2txtidx('Can - Live 1971-77');
Is there any good way of adding watches on any type of memory?
(I'm not that good with gdb -yet :))
Magnus
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
On Tue, 3 Dec 2002, Marc G. Fournier wrote: On Tue, 3 Dec 2002, Dave Page wrote: I could have sworn we used to have a bunch of ftp mirrors for downloads. Come to think of it I rewrote/stole a load of Vince's PHP code to allow you to select one from the portal recently. Are we not using them anymore? Yup, as with doing anything for the firs ttime, the press release itself had its 'bugs' ... considering how many times Josh asked for comments on it, I'm surprised that nobody picked up on it *shrug* I understood it was intentional so comments wouldn't have done any good. We are looking at some improvements to the download stuff ... Greg(?) suggested a layout that I really liked for a web based version that would have to tie into the main mirror database ... one that provided a wee bit more information then just the directory listings ... but, with that thought, isn't there a file you can put into an ftp directory that, when you web into that directory, i gives you the listings with various comments, or is that just using the .messages file? All of them I've seen had an index.html in it. Vince. -- http://www.meanstreamradio.com http://www.unknown-artists.com Internet radio: It's not file sharing, it's just radio. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] 7.4 Wishlist
Joe Conway writes: That is one thing I'd like to take a look at. I think the problem is that certain byte-sequence/multibyte-encoding combinations are illegal, so it's not as simple an issue as it might first appear. The bytea type really shouldn't come even close to having to care about this. Actually, if you want to improve the ugly bytea literal syntax, implement the standard BLOB type. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] MySQL update
Hi, I thought MySQL is marked as obsolete since PostgreSQL 7.3 ;-) Tommi Am Mittwoch, 4. Dezember 2002 03:55 schrieb Christopher Kings-Lynne: Not that anyone cares, but I notice in the commit logs for MySQL 4.1, it now has subselects. Chris ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] -- Dr. Eckhardt + Partner GmbH http://www.epgmbh.de ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] MySQL update
On 4 Dec 2002 at 8:13, Tommi Maekitalo wrote: I thought MySQL is marked as obsolete since PostgreSQL 7.3 ;-) If you ask me, one should never under-estimate the compitition..No matter how big upper hand you have.. If you want to compete in the first place, that is.. Bye Shridhar -- Ogden's Law:The sooner you fall behind, the more time you have to catch up. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
Dave Page wrote: snip I could have sworn we used to have a bunch of ftp mirrors for downloads. Come to think of it I rewrote/stole a load of Vince's PHP code to allow you to select one from the portal recently. Are we not using them anymore? Of course we are, it's just that we're also trying to direct people to the Advocacy site where there is a lot more info, in a lot more languages. The only reason for the download page not having a list of mirrors is due to not having done it yet. :-) Regards and best wishes, Justin Clift :-) Regards, Dave. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] -- My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there. - Indira Gandhi ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
Marc G. Fournier writes: Yup, as with doing anything for the firs ttime, the press release itself had its 'bugs' ... considering how many times Josh asked for comments on it, I'm surprised that nobody picked up on it *shrug* And how should we have guessed that release management is now done by the advocacy group? While you're out advocating, don't forget the existing users. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
Justin Clift writes: Of course we are, it's just that we're also trying to direct people to the Advocacy site where there is a lot more info, in a lot more languages. Why don't we just shut down the regular web site. Clearly it's not considered adequate anymore. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
Peter Eisentraut wrote: Marc G. Fournier writes: Yup, as with doing anything for the firs ttime, the press release itself had its 'bugs' ... considering how many times Josh asked for comments on it, I'm surprised that nobody picked up on it *shrug* And how should we have guessed that release management is now done by the advocacy group? While you're out advocating, don't forget the existing users. Sorry Peter. Regards and best wishes, Justin Clift -- My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there. - Indira Gandhi ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] [GENERAL] PostgreSQL Global Development Group Announces
Peter Eisentraut wrote: Justin Clift writes: Of course we are, it's just that we're also trying to direct people to the Advocacy site where there is a lot more info, in a lot more languages. Why don't we just shut down the regular web site. Clearly it's not considered adequate anymore. Well, qe're trying to move the new portal side of things into place (presently at wwwdevel.postgresql.org), so that all of the different PostgreSQL pieces are more easily accessible. Regards and best wishes, Justin Clift -- My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there. - Indira Gandhi ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
