Mats,
Patch applied. (I also fixed the 'length' problem you reported as well).
thanks,
--Barry
Mats Lofkvist wrote:
(I posted this on the bugs and jdbc newsgroups last week
but have seen no response. Imho, this really needs to
be fixed since the bug makes it impossible to use the
driver in a
On Tue, Nov 12, 2002 at 02:58:17PM -0400, Marc G. Fournier wrote:
if (ic_flag == 1) {
/*only select those non-IC/Spyder nodes that has full update set*/
EXEC SQL DECLARE full_dyn_node CURSOR FOR
SELECT node_name FROM NODE
WHERE
Tom Lane [EMAIL PROTECTED] wrote:
[snip]
Note that we have *zero* reports for any flavor of NetBSD and
OpenBSD.
Maybe they're both dead platforms? ;-)
Well, OpenBSD isn't dead :)
But i have problems compiling 7.3b5 on it (OpenBSD 3.1 i386).
I figured i should give it a go, since nobody
Yeah, we made an announcement to -general a few weeks ago, but didn't cross-post to
-hackers.
Cheers to all. Obviously as a co-founder of Great Bridge, I'm a big believer in
Postgres. OpenMFG makes extensive use of pl/pgsql for most of its ERP business logic.
We've also been beta testing
Magnus Naeslund(f) [EMAIL PROTECTED] wrote:
Well, OpenBSD isn't dead :)
But i have problems compiling 7.3b5 on it (OpenBSD 3.1 i386).
I figured i should give it a go, since nobody else did, but i get many
regression failures.
OK OK, before anyone rubs my nose in it, i see the fork()
On Sunday 10 November 2002 08:51 am, Hannu Krosing wrote:
snpe kirjutas L, 09.11.2002 kell 22:51:
Hello,
I work with JDeveloper and PostgreSQL JDBC and I have one problem.
I get error :
sub-SELECT in FORM must have an alias
I can't change SQL command, but it is internal JDeveloper
Hello,
When I change view and change number of column PostgreSQL return error :
'cannot change number of column in view'
Is it too hard set this command
if view exits drop view
and then change view
It is like with return type in function
Now 'or replace' don't help too much
regards
Justin Clift [EMAIL PROTECTED] writes:
We received a query through the Advocacy site about whether we support
AIX 5.1 or not, so am trying to find out.
It should work. Andreas just submitted a port confirmation on AIX
4.3.2 ...
regards, tom lane
Magnus Naeslund(f) [EMAIL PROTECTED] writes:
OK OK, before anyone rubs my nose in it, i see the fork() failures :)
I'll see what's causing the fork() problems...
Too low processes-per-user limit, likely.
regards, tom lane
---(end of
On Thu, Nov 14, 2002 at 13:41:18 +,
snpe [EMAIL PROTECTED] wrote:
Hello,
When I change view and change number of column PostgreSQL return error :
'cannot change number of column in view'
Is it too hard set this command
if view exits drop view
and then change view
It is like with
On Thursday 14 November 2002 02:41 pm, Bruno Wolff III wrote:
On Thu, Nov 14, 2002 at 13:41:18 +,
snpe [EMAIL PROTECTED] wrote:
Hello,
When I change view and change number of column PostgreSQL return error
: 'cannot change number of column in view'
Is it too hard set this
On Thu, 2002-11-14 at 11:17, snpe wrote:
On Thursday 14 November 2002 02:41 pm, Bruno Wolff III wrote:
On Thu, Nov 14, 2002 at 13:41:18 +,
snpe [EMAIL PROTECTED] wrote:
Hello,
When I change view and change number of column PostgreSQL return error
: 'cannot change number of
On Thursday 14 November 2002 04:38 pm, Rod Taylor wrote:
On Thu, 2002-11-14 at 11:17, snpe wrote:
On Thursday 14 November 2002 02:41 pm, Bruno Wolff III wrote:
On Thu, Nov 14, 2002 at 13:41:18 +,
snpe [EMAIL PROTECTED] wrote:
Hello,
When I change view and change number
On Thu, Nov 14, 2002 at 16:49:42 +,
snpe [EMAIL PROTECTED] wrote:
I want that 'create or replace view' work drop-create if view exists else only
create
Why do you want this?
---(end of broadcast)---
TIP 5: Have you checked our extensive
On Thursday 14 November 2002 05:01 pm, Bruno Wolff III wrote:
On Thu, Nov 14, 2002 at 16:49:42 +,
snpe [EMAIL PROTECTED] wrote:
I want that 'create or replace view' work drop-create if view exists else
only create
Why do you want this?
Why 'create or replace' ?
On Thu, Nov 14, 2002 at 17:00:30 +,
snpe [EMAIL PROTECTED] wrote:
On Thursday 14 November 2002 05:01 pm, Bruno Wolff III wrote:
On Thu, Nov 14, 2002 at 16:49:42 +,
snpe [EMAIL PROTECTED] wrote:
I want that 'create or replace view' work drop-create if view exists else
only
On Thursday 14 November 2002 05:22 pm, Bruno Wolff III wrote:
On Thu, Nov 14, 2002 at 17:00:30 +,
snpe [EMAIL PROTECTED] wrote:
On Thursday 14 November 2002 05:01 pm, Bruno Wolff III wrote:
On Thu, Nov 14, 2002 at 16:49:42 +,
snpe [EMAIL PROTECTED] wrote:
I want that
snpe [EMAIL PROTECTED] writes:
On Thursday 14 November 2002 05:22 pm, Bruno Wolff III wrote:
Are you trying to save typing a few characters or what?
Yes, it is 'create or replace view', not ?
The statement was not invented to save a few characters of typing.
It was invented to allow people to
Ports list updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
---
Patrick Welche wrote:
On Wed, Nov 13, 2002 at 07:53:00PM +0100, Peter Eisentraut wrote:
Tom Lane writes:
We can't
On Thu, Nov 14, 2002 at 06:13:56PM +, Patrick Welche wrote:
On Wed, Nov 13, 2002 at 07:53:00PM +0100, Peter Eisentraut wrote:
Tom Lane writes:
We can't just wait around indefinitely for port reports that may or may
not ever appear. In any case, most of the 7.3 entries in the list
Tom Lane wrote:
snpe [EMAIL PROTECTED] writes:
On Thursday 14 November 2002 05:22 pm, Bruno Wolff III wrote:
Are you trying to save typing a few characters or what?
Yes, it is 'create or replace view', not ?
The statement was not invented to save a few characters of typing.
It was
Philip Warner [EMAIL PROTECTED] writes:
At 12:39 AM 14/11/2002 -0500, Neil Conway wrote:
Perhaps when the function is defined, we run all the SQL queries in
the function body through the parser/analyzer/rewriter, and then
generate dependencies on the Query trees we get back?
Won't work for
On Thu, 14 Nov 2002, Scott Shattuck wrote:
It might just be me but it seems that this discussion is missing the
point if we believe this request is about saving some characters. I
don't think it is. I think it's about being able to write simple SQL
scripts that don't produce errors when you
Believe it or not, I'm trying to compile today's cvs pgsql on a
Debian 2.2.19 system. Compilation dies while compiling pg_dump with
../../../src/interfaces/libpq/libpq.so: undefined reference to `atexit'
In the mail archives there is a mention of upgrading libc to
libc6-dev_2.2.5-3_i386.deb. As
Patrick Welche [EMAIL PROTECTED] writes:
Believe it or not, I'm trying to compile today's cvs pgsql on a
Debian 2.2.19 system. Compilation dies while compiling pg_dump with
../../../src/interfaces/libpq/libpq.so: undefined reference to `atexit'
blink Did you run configure? AFAICT that call
On Thursday 14 November 2002 05:45 pm, Tom Lane wrote:
snpe [EMAIL PROTECTED] writes:
On Thursday 14 November 2002 05:22 pm, Bruno Wolff III wrote:
Are you trying to save typing a few characters or what?
Yes, it is 'create or replace view', not ?
The statement was not invented to save a
Tom Lane wrote:
Seriously, I agree with Marc's opinion that issuing an RC1 is the best
way to flush out some more port reports. I do not know what else we can
do to get people off their duffs and onto last-minute testing.
If testing is the problem, I think publicizing the betas would help
On Thursday 14 November 2002 08:01 pm, Stephan Szabo wrote:
On Thu, 14 Nov 2002, Scott Shattuck wrote:
It might just be me but it seems that this discussion is missing the
point if we believe this request is about saving some characters. I
don't think it is. I think it's about being able to
On Thu, 14 Nov 2002, snpe wrote:
Problem is when I want change view (or functions) with a lot of dependecies
I must drop and recreate all dependent views (or functions) - I want add only
one column in view
I don't know if solution hard for that.
Well, doing create or replace as a
Sorry, I was vague. I think we should apply and go to RC1 tomorrow.
There will always be tweaks and fixes. If we expect it to be perfect,
we will never make a final release. We are 2.5 months into beta, and
if we don't want +3 months beta, we should get going.
We have to start taking
Problem is when I want change view (or functions) with a lot of
dependecies
I must drop and recreate all dependent views (or functions) - I
want add only
one column in view
I don't know if solution hard for that.
This is definitely something that will cause some anguish in 7.3. I think
7.4
Hi Guys,
I emailed a few people to try to get some platform reports. What was the
solution to this problem? It was AWK or something wasn't it? Will Martin
have to try RC1?
Chris
We are trying to get our supported platforms list together, and
so far we
have not had any platform reports
On Thursday 14 November 2002 10:36 pm, Stephan Szabo wrote:
On Thu, 14 Nov 2002, snpe wrote:
Problem is when I want change view (or functions) with a lot of
dependecies I must drop and recreate all dependent views (or functions) -
I want add only one column in view
I don't know if
Well, doing create or replace as a drop/create might very well
do the same
thing, and even if it got the same oid, we'd have to be really sure that
nothing would misbehave upon receiving that extra column before allowing
it for purposes of avoiding recreation of dependencies.
Can
I'd like to implement FOR EACH STATEMENT triggers. AFAICS it shouldn't
be too tricky -- so if there's some show-stopper that prevented it
from being done earlier, let me know now, please :-)
Some random notes on the implementation I'm thinking of:
- in the function called by a
On Sunday 10 November 2002 08:51 am, Hannu Krosing wrote:
snpe kirjutas L, 09.11.2002 kell 22:51:
Hello,
I work with JDeveloper and PostgreSQL JDBC and I have one problem.
I get error :
sub-SELECT in FORM must have an alias
I can't change SQL command, but it is internal
Looks pretty sweet, Neil.
Maybe you could look at column triggers while you're at it, per comment on
Compiere page ;)
Triggers
Compiere uses triggers to ensure data consistency. It seems that in general,
Oracle triggers are relatively easy to convert. In addition to the Function
issues, a
Christopher Kings-Lynne wrote:
Sorry, I was vague. I think we should apply and go to RC1 tomorrow.
There will always be tweaks and fixes. If we expect it to be perfect,
we will never make a final release. We are 2.5 months into beta, and
if we don't want +3 months beta, we should get
It was Solaris awk. The fix will be in RC1.
---
Christopher Kings-Lynne wrote:
Hi Guys,
I emailed a few people to try to get some platform reports. What was the
solution to this problem? It was AWK or something
I have moved more variables into the log_* GUC category in an attempt to
make log control more understandable. Changes to postgresql.conf
attached.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a
On Thu, 14 Nov 2002, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
If we are going to go for a beta6, I vote we reverse out the patch. Of
course, I prefer neither.
I read this several times and am still not quite sure which path you are
voting for. We can:
1. not apply the
Ross J. Reedstrom [EMAIL PROTECTED] writes:
I've tested this under 7.3, and it works beautifully for the cases I've
built over the last 2 days. I can no longer bugger a plan up mearly
by reordering the WHERE clauses. Note that 2 of the five parts won't
patch in (involving constantqual). Looks
I'd ask for a quick beta6 ... even knowing everyone would hate me :)
On Thu, 14 Nov 2002, Tom Lane wrote:
I said:
Well, we could define it as a bug ;-) --- that is, a performance regression.
I'd be happier about adding a dozen lines of code to sort quals by
whether or not they contain
If we are going to go for a beta6, I vote we reverse out the patch. Of
course, I prefer neither.
Do we have to do a delay/feature analysis on this?
Marc, there will always be 7.3.1 to fix any problems. They will surely
happen so I think it is safe to push forward for tomorrow's RC1. Of
Marc G. Fournier [EMAIL PROTECTED] writes:
I'd ask for a quick beta6 ... even knowing everyone would hate me :)
What's wrong with calling it RC1?
I think pushing out an RC tarball is the only way we'll shake loose any
more port reports. Putting out beta6 isn't going to attract attention
from
Bruce Momjian [EMAIL PROTECTED] writes:
If we are going to go for a beta6, I vote we reverse out the patch.
It's not applied yet.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Bruce Momjian [EMAIL PROTECTED] writes:
If we are going to go for a beta6, I vote we reverse out the patch. Of
course, I prefer neither.
I read this several times and am still not quite sure which path you are
voting for. We can:
1. not apply the patch to fix Ross' problem, and ship RC1
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
If we are going to go for a beta6, I vote we reverse out the patch. Of
course, I prefer neither.
I read this several times and am still not quite sure which path you are
voting for. We can:
1. not apply the patch to fix Ross'
Bruce Momjian wrote:
Tom Lane wrote:
snip
Personally I think this is a low-risk patch and so choice 2 is
appropriate.
If this is the only change, then 2 does seem like the best mix of
risk/progress.
:-)
Regards and best wishes,
Justin Clift
Sorry, I was vague. I think we should
Tom Lane [EMAIL PROTECTED] writes:
2. apply the patch, and ship RC1 tomorrow;
I think that's the best bet.
(That said, the philosophy of there's always 7.3.1 that Bruce alluded
to is not one that I agree with.)
Cheers,
Neil
--
Neil Conway [EMAIL PROTECTED] || PGP Key ID: DB3C29FC
Justin Clift wrote:
Tom Lane wrote:
Justin Clift [EMAIL PROTECTED] writes:
We received a query through the Advocacy site about whether we support
AIX 5.1 or not, so am trying to find out.
It should work. Andreas just submitted a port confirmation on AIX
4.3.2 ...
Thanks Tom.
Tom Lane [EMAIL PROTECTED] wrote:
Too low processes-per-user limit, likely.
Yes, ofcourse...
This is what happens when you're in a hurry and tries to make everything
happen at the same time :)
Now it all passes:
OpenBSD 3.1 i386
./configure \
--with-perl\
--enable-odbc
Ports list updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
Also, I assume the (f) is part of your name, right?
---
Magnus Naeslund(f) wrote:
Tom Lane [EMAIL PROTECTED] wrote:
Too low
Bruce Momjian [EMAIL PROTECTED] wrote:
Ports list updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-
platforms.html
Also, I assume the (f) is part of your name, right?
Cool.
No the (f) part is really a mail account thing that (I/we)'ve
traditionally had.
If it's (w)
Thanks. Fixed.
---
Magnus Naeslund(f) wrote:
Bruce Momjian [EMAIL PROTECTED] wrote:
Ports list updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-
platforms.html
Also, I assume the (f) is
We received a query through the Advocacy site about whether we support
AIX 5.1 or not, so am trying to find out.
It should work. Andreas just submitted a port confirmation on AIX
4.3.2 ...
Do you feel there's anyone around that would be able to give a
definitite yes or no?
Zeugswetter Andreas SB SD wrote:
I don't have AIX 5 here, so cannot test, sorry.
But yes, it should definitely work.
There is a known possible performance improvement for concurrent sessions on
multiprocessor AIX machines. The now depricated cs(3) used for the AIX TAS
implementation
I don't have AIX 5 here, so cannot test, sorry.
But yes, it should definitely work.
There is a known possible performance improvement for concurrent sessions on
multiprocessor AIX machines. The now depricated cs(3) used for the AIX TAS
implementation should be replaced with
Zeugswetter Andreas SB SD wrote:
I don't have AIX 5 here, so cannot test, sorry.
But yes, it should definitely work.
There is a known possible performance improvement for concurrent sessions on
multiprocessor AIX machines. The now depricated cs(3) used for the AIX TAS
Ross J. Reedstrom [EMAIL PROTECTED] writes:
Sorry to be a pest, but I'd like to re-raise the issue I brought up
regarding a performance regression from 7.2.3, when subqueries are pulled
up and merged with their parent.
...
Tom was not excited about making the original change (we don't
On Wed, Nov 13, 2002 at 07:53:00PM +0100, Peter Eisentraut wrote:
Tom Lane writes:
We can't just wait around indefinitely for port reports that may or may
not ever appear. In any case, most of the 7.3 entries in the list
seem to be various flavors of *BSD; I think it's unlikely we broke
I said:
Well, we could define it as a bug ;-) --- that is, a performance regression.
I'd be happier about adding a dozen lines of code to sort quals by
whether or not they contain a subplan than about flip-flopping on the
original patch. That would actually solve the class of problem you
Tom, would you really be able to ask Permaine to retest 7.3? Have a
feeling we might be able to leverage the PlayStation2 brand name here
for the Advocacy project.
:-)
Anyone try it on an Xbox yet?
---(end of broadcast)---
TIP 6: Have you
Just a quick note to mention that I've resigned from the PostgreSQL
steering committee. It has been a lot of fun and very rewarding to
participate in PostgreSQL development over the last six years, but it is
time to take a break and to move on to other projects.
Thanks to Marc, Bruce, and
Just a quick note to mention that I've resigned from the PostgreSQL
steering committee. It has been a lot of fun and very rewarding to
participate in PostgreSQL development over the last six years, but it is
time to take a break and to move on to other projects.
Thanks for all your work,
Thomas Lockhart wrote:
Just a quick note to mention that I've resigned from the PostgreSQL
steering committee.
Wow. That was totally unexpected.
A sad day. :-/
It has been a lot of fun and very rewarding to
participate in PostgreSQL development over the last six years, but it is
time
66 matches
Mail list logo
