> After our and the pg7.3 release is out we'll port there and I
> really would like
> to get rid of this restriction with that release than. So it
> would be wonderful
> if that still goes into the final of 7.3.
I'm not a core developer, but I'll tell you right now that there's pretty
much zero ch
Stephan Szabo wrote:
> I've been working on something of the sort. I've got a test patch
> (against about 7.3b2) that I'm trying to validate which cases it does and
> does not work for. I'm still looking for more volunteers if you've got a
> dev system you're willing to use. :)
I'd willing to do
Hi guys,
We received a query through the Advocacy site about whether we support
AIX 5.1 or not, so am trying to find out.
Just took a look at the Supported Platforms list, and the FAQ_AIX
document (for 7.2.x) and it doesn't seem to mention specific versions of
AIX that are supported.
Does Postgr
Tom Lane wrote:
> Anyone care about the PlayStation 2 port ;=) ? I can get Permaine to
> retest if so. Slightly more seriously, we did see a recent report of
> trouble on S/390 Linux, but the complainant didn't follow up...
Heh Heh Heh
Tom, would you really be able to ask Permaine to retest 7.
Neil Conway wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> > > Anyone care about the PlayStation 2 port ;=) ? I can get Permaine to
> > > retest if so. Slightly more seriously, we did see a recent report of
> > > trouble on S/390 Linux, but the complainant didn't follow
Philip Warner <[EMAIL PROTECTED]> writes:
> Won't work for functions that build dynamic queries.
Granted, but the the intent is to
(a) solve some, but not necessarily all, of the dump-order
problems
(b) drop functions that depend on a database object when the
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 functions that build dynamic queries. But it
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
> > Anyone care about the PlayStation 2 port ;=) ? I can get Permaine to
> > retest if so. Slightly more seriously, we did see a recent report of
> > trouble on S/390 Linux, but the complainant didn't follow up...
>
> I put an S/390 pat
Tom Lane <[EMAIL PROTECTED]> writes:
> * We don't store dependencies for SQL functions to things mentioned in
> the SQL function body. (Maybe we should, but we don't.) So there's
> data missing in that case, and possibly other cases.
This might be interesting to do, and we could tie it into the
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> It's an ERP company, OpenMFG, that uses Linux, PostgreSQL and QT. In the
> article they say they're active in Postgres development. Just wondering if
> they wanted to say hi!
While we're on the topic, it appears that Compiere (www.compiere.
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> How shall we distinguish your version of freebsd from the ones that
>> need the other comparison file?
> He is using the FreeBSD 3.x series (which is quite old now), whereas most
> people are probably using 4.x. I have no problems with regr
Christopher Kings-Lynne wrote:
> I just came across this article:
>
> http://newsforge.com/newsforge/02/11/11/1848223.shtml?tid=3
>
> It's an ERP company, OpenMFG, that uses Linux, PostgreSQL and QT. In the
> article they say they're active in Postgres development. Just wondering if
> they want
I just came across this article:
http://newsforge.com/newsforge/02/11/11/1848223.shtml?tid=3
It's an ERP company, OpenMFG, that uses Linux, PostgreSQL and QT. In the
article they say they're active in Postgres development. Just wondering if
they wanted to say hi!
Chris
-
Christopher Kings-Lynne wrote:
> > > 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
> > > those ...
> >
> > Note that we have
I added it to the ports list as OK. We can deal with fixing the
regression falure independently.
---
Nigel J. Andrews wrote:
> On Wed, 13 Nov 2002, Tom Lane wrote:
>
> > "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> >
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > It seems to me that about the only major issue right now is testing the
> > various platforms ... would anyone disagree with putting out an RC1 on
> > Friday whose primary purpose is platform testing?
>
> Works for me. We should
At 02:53 PM 13/11/2002 -0500, Rod Taylor wrote:
I can make a complete list tonight of whats captured.
Sounds good.
If you can also indicate which parts of functions are captured - arguments,
return type and body? IIRC, only SQL functions are compiled at define-time,
so other functions *should
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > 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
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> 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
>> those ...
> N
Ports list updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
---
Nigel J. Andrews wrote:
> On Tue, 12 Nov 2002, Tom Lane wrote:
>
> > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > > Br
I have installed a 128k ISDN line to my home to service candle.pha.pa.us
& momjian.postgresql.org. You should be seeing the same performance you
saw while I was in my old house pre-August.
I hope ADSL will reach my house within the next year.
--
Bruce Momjian| http://
> The thought that I'd been toying with is to build a list of inter-object
> dependencies (using pg_depend if available, else fall back on pg_dump's
> native wit, ie, the rather limited set of dependencies it already
> understands). Then do a topological sort, preferring to maintain OID
> order in
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > FWIW, gmake check and gmake bigcheck pass on:
> > FreeBSD 3.3-RELEASE #3: Thu Feb 3 23:48:56 GMT 2000
>
> > with the expection of:
> > [snipped]
> > in the float8 test.
>
> Okay, looks like we need to use float8-fp-exception.out on your
> platfo
> > 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
> > those ...
>
> Note that we have *zero* reports for any flavor of NetBSD an
On Wed, 13 Nov 2002, Peter Schindler wrote:
> But, if a lot of inserts happens into the child table and there is a
> mix of short and long running transactions, the likelihood of blocking
> is very high, even the inserts are independent and everything is ok
> (prim. key etc.). This is even more e
I've got a question about the foreign key constraint behavior.
It looks to me that inserts within transactions into a child table, which have the
same FK value back to the parent will block until the first txn will commit or
rollback. (see example below)
This seems to be based on the fact that
> Do we have a list of dependency data that we collect? eg. do we know about
> functions used in views and indexes? At this stage it's probably worth
> - constraints
> - sequences set (not really a dependency problem)
> - indexes
> - comments
I can make a complete list tonight of whats captured
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> I don't know anything about how the tests are put together so I'd have
> to look into that before suggesting a way to differentiate my
> system. Having said that wouldn't the 3.3-RELEASE string be
> sufficient?
The mechanism we have in place relies
On Wed, 13 Nov 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > FWIW, gmake check and gmake bigcheck pass on:
> > FreeBSD 3.3-RELEASE #3: Thu Feb 3 23:48:56 GMT 2000
>
> > with the expection of:
> > [snipped]
> > in the float8 test.
>
> Okay, looks like we need to use
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> FWIW, gmake check and gmake bigcheck pass on:
> FreeBSD 3.3-RELEASE #3: Thu Feb 3 23:48:56 GMT 2000
> with the expection of:
> [snipped]
> in the float8 test.
Okay, looks like we need to use float8-fp-exception.out on your
platform. This is a bit
On Tue, 12 Nov 2002, Tom Lane wrote:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > Ok, now that I've run it that way, the last couple of pages of output
> > look like this:
>
> Hm. So the "while read line" loop is iterating only once.
>
> I was thinking to myself that something within the
On Wed, 13 Nov 2002 10:06:15 EST, the world broke into rejoicing as
Tom Lane <[EMAIL PROTECTED]> said:
> "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> > Why use awk for this at all ? and not:
> > echo "\\set ECHO all"
>
> I think Bruce is worried about portability; some versions of ec
> "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
>> Why use awk for this at all ? and not:
>> echo "\\set ECHO all"
Actually, some googling revealed the following advice (in the Autoconf
manual):
Because of these problems, do not pass a string containing
arbitrary characters to
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> It seems to me that about the only major issue right now is testing the
> various platforms ... would anyone disagree with putting out an RC1 on
> Friday whose primary purpose is platform testing?
Works for me. We should be able to resolve this awk
It seems to me that about the only major issue right now is testing the
various platforms ... would anyone disagree with putting out an RC1 on
Friday whose primary purpose is platform testing? I don't believe there
is anything outstanding right now that would require us to do a beta6, and
RC1 mig
At 09:29 AM 13/11/2002 -0500, Rod Taylor wrote:
An ALAP scheduling algorithm will almost always sort these things to be
side by side to allow combining on a second pass by something with the
intelligence.
Do we have a list of dependency data that we collect? eg. do we know about
functions used
Philip Warner <[EMAIL PROTECTED]> writes:
> The suggestion of breaking items into create/alter etc is interesting - I
> assume you are thinking of function bodies? Or is there something else?
Let's see --- foreign-key constraints are an obvious source of possible
circularities, but I see pg_dump
You're right, I should remove that (cruft left over from when the
subselect wasn't). However, it has no impact on the planner at hand:
removing it does trim 25% from the execution time, but getting the
WHERE clauses used in the right order gains an order of magnitude.
Both apply. Thanks, I'll fix
On Wed, Nov 13, 2002 at 08:58:04AM -0500, Tom Lane wrote:
> "Ross J. Reedstrom" <[EMAIL PROTECTED]> writes:
> > Bingo, that solved it. I'm back to 160 ms. What does Tom feel about
> > removing this? Is there some way the planner could have known which
> > was the smarter/faster order of application
"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> Why use awk for this at all ? and not:
> echo "\\set ECHO all"
I think Bruce is worried about portability; some versions of echo might
do something weird with the backslash. OTOH, it's not obvious to me
that awk is better on that score. B
"Mario Weilguni" <[EMAIL PROTECTED]> writes:
> I noticed that the planner is unable to select an index scan when a partial
> index is available, the partial index is based on a "NOT NULL" condition.
It wants you to do this:
select id from str where url='foobar' and url is not null;
I know and yo
On Wed, 2002-11-13 at 09:08, Philip Warner wrote:
> At 08:52 AM 13/11/2002 -0500, Rod Taylor wrote:
> >The biggest trick will be trying to re-combine the ALTER ... ADD
> >CONSTRAINT and ALTER ... SET DEFAULT statements back into CREATE TABLE
>
> I'm not sure this would be worth the effort - I'll g
At 08:52 AM 13/11/2002 -0500, Rod Taylor wrote:
The biggest trick will be trying to re-combine the ALTER ... ADD
CONSTRAINT and ALTER ... SET DEFAULT statements back into CREATE TABLE
I'm not sure this would be worth the effort - I'll grant it would be cute,
but getting pg_dump to understand S
At 01:50 PM 13/11/2002 +0800, Christopher Kings-Lynne wrote:
Well, the problem is that you can add a new type and then add a column to a
really old table that uses that type - that causes pain\
You may have misunderstood; I meant to add each type used by the table to
the deps list for a table (
"Ross J. Reedstrom" <[EMAIL PROTECTED]> writes:
> Bingo, that solved it. I'm back to 160 ms. What does Tom feel about
> removing this? Is there some way the planner could have known which
> was the smarter/faster order of application?
As I said in the previous thread, I don't have a lot of patienc
> My suspicion falls on the very-recently-added awk calls. Try changing
>
> (echo "SET autocommit TO 'on';"; awk 'BEGIN {printf
> "\\set ECHO all\n"}'; cat "$inputdir/sql/$1.sql") |
Why use awk for this at all ? and not:
echo "\\set ECHO all"
??
Andreas
---(en
>You can try an index like:
>create index str_idx_url on str(url) where url >= '';
>
>I think that should be identical. ('' is the smallest string, no ?)
Thanks alot, it works now. But I still think the NOT NULL case would be
useful.
Best regards,
Mario Weilguni
> mydb=# create index str_idx_url on str(url) where url is not null;
> CREATE
> mydb=# analyze str;
> ANALYZE
> mydb=# EXPLAIN ANALYZE select id from str where url='foobar';
> NOTICE: QUERY PLAN:
>
> Seq Scan on str (cost=0.00..91.05 rows=3 width=4) (actual
You can try an index like:
create i
I noticed that the planner is unable to select an index scan when a partial
index is available, the partial index is based on a "NOT NULL" condition.
Example:
start with no index:
mydb=# EXPLAIN ANALYZE select id from str where url='foobar';
NOTICE: QUERY PLAN:
Seq Scan on str (cost=0.00..88.9
On Tue, 12 Nov 2002, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Bruce Momjian writes:
> >> Are we ready for RC1 yet?
>
> > Questionable. We don't even have 50% confirmation coverage for the
> > supported platforms yet.
>
> We can't just wait around indefinitely for port
(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 multithreaded environment so I'm reposting
to hackers and patches.)
_
Mats Lofkvist
[EMAIL PROTECTED]
The optim
Marc,
Marc G. Fournier writes:
> 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 dynamic_community = 'f' AND ic_f
Am Mittwoch, 13. November 2002 07:22 schrieb Ross J. Reedstrom:
> Hey Hackers -
...
>
> CREATE VIEW current_modules AS
>SELECT * FROM modules m
> WHERE module_ident =
> (SELECT max(module_ident) FROM modules
> WHERE m.moduleid =
On Wed, Nov 13, 2002 at 02:40:40AM -0500, Mike Mascari wrote:
> Ross J. Reedstrom wrote:
> >
> >For this query, the difference is 160 ms vs. 2 sec. Any reason for this
> >change?
>
> I could be way off base, but here's a shot in the dark:
>
>
>http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&o
54 matches
Mail list logo
