Re: [GENERAL] outer join fails with error - solaris only
[EMAIL PROTECTED] writes: > The following query gives an error when run on solaris 2.7, but it works > fine with an equivalent configuration on rh 6.2. It probably has nothing to do with the platform, but rather with when you last ran VACUUM ANALYZE and what the exact contents of the database were at the time. Does the problem become reproducible on both platforms if you do SET enable_hashjoin TO off; SET enable_nestloop TO off; > ERROR: RIGHT JOIN is only supported with mergejoinable join conditions I believe this is fixed in 7.1.1 --- sounds like the same bug as 2001-04-14 20:48 tgl * src/backend/optimizer/path/joinpath.c: Prevent generation of invalid plans for RIGHT or FULL joins with multiple join clauses. The mergejoin executor wants all the join clauses to appear as merge quals, not as extra joinquals, for these kinds of joins. But the planner would consider plans in which partially-sorted input paths were used, leading to only some of the join clauses becoming merge quals. This is fine for inner/left joins, not fine for right/full joins. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[GENERAL] outer join fails with error - solaris only
The following query gives an error when run on solaris 2.7, but it works
fine with an equivalent configuration on rh 6.2.
select tr.transition_key,
tr.transition_name
from wf_transition_info tr
left outer join
wf_context_assignments ca
on (tr.context_key = ca.context_key and
tr.transition_key = ca.transition_key)
where tr.workflow_key = 'expenses_wf'
and tr.context_key = 'default'
and tr.trigger_type = 'user'
and tr.assignment_callback is null;
.
.
.
DROP
CREATE
psql:tst.sql:210: ERROR: RIGHT JOIN is only supported with mergejoinable join
conditions
acspg=# select version();
version
-
PostgreSQL 7.1 on sparc-sun-solaris2.7, compiled by GCC 2.7.2.2
(1 row)
acspg=#
The following code can be used to reproduce the error:
drop table wf_workflows;
create table wf_workflows (
workflow_key varchar(100)
constraint wf_workflows_pk
primary key,
description text
);
drop table wf_contexts;
create table wf_contexts (
context_key varchar(100)
constraint wf_context_pk
primary key,
context_name varchar(100)
constraint wf_contexts_context_name_nn
not null
constraint wf_contexts_context_name_un
unique
);
drop table wf_transitions;
create table wf_transitions (
transition_keyvarchar(100),
transition_name varchar(100)
constraint wf_transition_name_nn
not null,
workflow_key varchar(100)
constraint wf_transition_workflow_fk
references wf_workflows(workflow_key)
on delete cascade,
-- purely for UI purposes
sort_orderinteger
constraint wf_transition_order_ck
check (sort_order > 0),
trigger_type varchar(40)
constraint wf_transition_trigger_type_ck
check (trigger_type in
('','automatic','user','message','time')),
constraint wf_transition_pk
primary key (workflow_key, transition_key),
constraint wf_trans_wf_key_trans_name_un
unique (workflow_key, transition_name)
);
drop table wf_context_transition_info;
create table wf_context_transition_info (
context_key varchar(100)
constraint wf_context_trans_context_fk
references wf_contexts,
workflow_key varchar(100)
constraint wf_context_trans_workflow_fk
references wf_workflows,
transition_keyvarchar(100),
/* information for the transition in the context */
/* The integer of minutes this task is estimated to take */
estimated_minutes integer,
/*
* Will be called when the transition is enabled/fired.
* signature: (case_id in integer, transition_key in varchar, custom_arg in varchar2)
*/
enable_callback varchar(100),
enable_custom_arg text,
fire_callback varchar(100),
fire_custom_arg text,
/*
* Must insert rows into the wf_task_assignments table.
* Will be called when the transition becomes enabled
* signature: (task_id in integer, custom_arg in varchar)
*/
assignment_callback varchar(100),
assignment_custom_arg text,
/*
* Must return the date that the timed transition should fire
* Will be called when the transition is enabled
* signature: (case_id in integer, transition_key in varchar, custom_arg in
varchar2) return date
*/
time_callback varchar(100),
time_custom_arg text,
/*
* Returns the deadline for this task.
* Will be called when the transition becomes enabled
* Signature: (case_id in integer, transition_key in varchar, custom_arg in
varchar2) return date
*/
deadline_callback varchar(100),
deadline_custom_arg text,
/* The name of an attribute that holds the deadline */
deadline_attribute_name varchar(100),
/*
* Must return the date that the user's hold on the task times out.
* called when the user starts the task.
* signature: (case_id in integer, transition_key in varchar, custom_arg in
varchar2) return date
*/
hold_timeout_callback varchar(100),
hold_timeout_custom_arg text,
/*
* Notification callback
* Will be called when a notification is sent i.e., when a transition is enabled,
* or assignment changes.
* signature: (task_idin integer,
Re: [GENERAL] Backward migration
I think you should post the exact errors you're getting to the mailing list, so maybe someone can help you. Valerio Santinelli Digisoft Multimedia http://www.digisoftmultimedia.it/ - Original Message - From: "Francisco M. Marzoa Alonso" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 17, 2001 12:18 PM Subject: [GENERAL] Backward migration > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi there, > > I must migrate a PostgreSQL database that I've created initially with > PostgreSQL 7.0 over LiNUX to a system that has PostgreSQL 6.5.3 running on a > FreeBSD. I've no chance to update de PostgreSQL engine to a newer version so > the only way for me to do this is migrating the data. > > I've used pg_dump ... and psql -e ... to do this, but I've obtained a lot of > errors and, finally, a segmentation fault; Of course, database is not > created. It seems like 6.5.3 version couldn't understand some of the commands > or the syntax generated by pg_dump on 7.0. > > Help??? > > Thanks (a lot) in advance, > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iEYEARECAAYFAjsDpYkACgkQdcZSl+4pW25qjwCdGkX/HjO+pN0s85wTwetRLctO > vtYAnjyJ/02zDW4RQHMOe7ihdzPVLgBY > =pWVE > -END PGP SIGNATURE- > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster > ---(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: [GENERAL] Restore from a dead machine.
Thanks all for the help. I've got it working. I remade the perl module and found that there were some directories/files it wanted to write to that it couldn't. So i allowed those permissions and remade install and everything worked swell. thanks for the help. .jtp ---(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: [GENERAL] Restore from a dead machine.
I've seen this message before - it appears when, like you indicated, the specified module can't be found in any of the directories specified in the Perl @INC array. If you can locate the Pg.pm module on your system, copy it to one of the directories specified (a symbolic link might work, too, but I've not tried that). Another option might be to download and install the latest Pg module from CPAN. Best Regards, User JOHN wrote: > On Wed, 16 May 2001, Tom Lane wrote: > > > User JOHN <[EMAIL PROTECTED]> writes: > > > But when i try to run any of the perl scripts designed for the database > > > I'm getting the following error: > > > > > Can't locate Pg.pm in @INC (@INC contains: /usr/libdata/perl/5.00503/mach > > > /usr/libdata/perl/5.00503 > > > /usr/local/lib/perl5/site_perl/5.005/i386-freebsd > > > /usr/local/lib/perl5/site_perl/5.005 .) at ./top25.pl line 2. > > > > Perhaps what it's really failing to find is libpq.so. Are you sure your > > dynamic loader's search path will find libpq? > > > > regards, tom lane > > I was having trouble with libraries prior to this perl issue. I've since > fixed this issue (the libpq.so) but the Perl issue remains. > I've looked in all the directories implicated and none of them hold Pg.pm. > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster -- John Burski Data Processing Manager 911EP First in LEDs... The solid state warning light leader. 1-800-863-6911 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [GENERAL] Need help using PHP ODBC to connect Postgress 7.1.1
--- Hiroshi Inoue <[EMAIL PROTECTED]> wrote: > Allan Rafuse wrote: > > > > I'm having trouble setting up a remote Apache PHP webserver > to connect to > > our postgres machine using ODBC. > > > > Are you using ~/.odbc.ini(user DSN) for odbc.ini ? > Current psqlodbc driver doesn't understand system DSN. System DSN works fine for me. Brent __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] Restore from a dead machine.
On Wed, 16 May 2001, Tom Lane wrote: > User JOHN <[EMAIL PROTECTED]> writes: > > But when i try to run any of the perl scripts designed for the database > > I'm getting the following error: > > > Can't locate Pg.pm in @INC (@INC contains: /usr/libdata/perl/5.00503/mach > > /usr/libdata/perl/5.00503 > > /usr/local/lib/perl5/site_perl/5.005/i386-freebsd > > /usr/local/lib/perl5/site_perl/5.005 .) at ./top25.pl line 2. > > Perhaps what it's really failing to find is libpq.so. Are you sure your > dynamic loader's search path will find libpq? > > regards, tom lane I was having trouble with libraries prior to this perl issue. I've since fixed this issue (the libpq.so) but the Perl issue remains. I've looked in all the directories implicated and none of them hold Pg.pm. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[GENERAL] Backward migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I must migrate a PostgreSQL database that I've created initially with PostgreSQL 7.0 over LiNUX to a system that has PostgreSQL 6.5.3 running on a FreeBSD. I've no chance to update de PostgreSQL engine to a newer version so the only way for me to do this is migrating the data. I've used pg_dump ... and psql -e ... to do this, but I've obtained a lot of errors and, finally, a segmentation fault; Of course, database is not created. It seems like 6.5.3 version couldn't understand some of the commands or the syntax generated by pg_dump on 7.0. Help??? Thanks (a lot) in advance, -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjsDpYkACgkQdcZSl+4pW25qjwCdGkX/HjO+pN0s85wTwetRLctO vtYAnjyJ/02zDW4RQHMOe7ihdzPVLgBY =pWVE -END PGP SIGNATURE- ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[GENERAL] Timestamp Format
how can I make a timestamp data type be outputted without the time zone? I expect: "-MM-DD HH:MM:SS" instead of postgresql output: "-MM-DD HH:MM:SS-timezone" I know I can do that by using some functions on the select query, but my idea is to get this result without altering the queries, like changing an enviroment variable or a setting in the configuration file or whatever like that, but NOT in the query. from what I've read so far, set DATETYLE won't help at all, it just changes the way the date and the timezone is printed, but it won't ouput a strict '-MM-DD HH:MM:SS' can postgresql do this at all (once again, without using functions or altering the query) Thanks in advance, Alex ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
