I've posted RPMs for Mandrake, but could not put them in the obvious
place on the FTP site because the permissions do not allow group write
access. Lamar, could you open up that part of the tree to allow group
write permissions? In the meantime, I've placed the files in
First pleasu use a subject line, since I almost discarded this
message.
Second please send your questions to an appropriate list like
pgsql-general.
See if adding the next row is fast again.
If it is not, I do not have a clue.
Andreas
-Ursprüngliche Nachricht-Von: Saju
A fellow NetBSD developer has sent me some changes needed to build 7.1
cleanly on NetBSD through its package system. I am asking him a few
questions about it but I thought I would just commit them then if no one
has a problem. They are mostly related to building cleanly on NetBSD.
Perhaps
Hi.
After `configure --enable-depend' I try `make' and got
gmake[3]: Entering directory
`/tmp_mnt/hosts/wisdom/NewSoftware/Ask/build/pgsql/src/backend/port'
gcc -Wall -Wmissing-prototypes -Wmissing-declarations
-I../../../src/include -c -o ../../utils/strdup.o ../../utils/strdup.c
-MMD
cp:
Thomas Lockhart [EMAIL PROTECTED] writes:
I've built RPMs for 7.1.1, but perhaps we should wait until 7.1.2 to
post them given the pgtcl problem? Lamar, what are you planning for
7.1.1?
Given my plpgsql screwup, and the dump-7.0-views thing that Philip wants
to fix in pg_dump, I'd say there
Fiddling with userlock stuff for the purposes of setting up an action
queue. Having the lock in the where clause causes the lock code to
actually lock 2 rows, not just the one that is being returned. 0's in
the last section means it could not be locked. This is with 7.1.1.
The function itself
Kovacs Zoltan [EMAIL PROTECTED] writes:
I cannot decide if this is a serious bug or not --- some queries from
complex views may give strange results. The next few days I will try to
find the point where the problem is but now I can only include the data
structure and the SELECT statements
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
A fellow NetBSD developer has sent me some changes needed to build 7.1
cleanly on NetBSD through its package system. I am asking him a few
questions about it but I thought I would just commit them then if no one
has a problem. They are mostly
Hi.
On some systems /bin/sh is not Burne Shell, e.g. /bin/sh is tcsh, but
there is /bin/sh5. It is looks like there is already knowledge about it in
the system: Makefile.ultrix4 has `SHELL=/bin/sh5' in it, but configure
thinks something else: config.status has `s%@SHELL@%/bin/sh%g'. (This is
HOWEVER, I _do_ have 7.1.1 RPMs built (minus some minor modifications) for
RedHat 7.1. Thomas, would you mind e-mailing me any changes you made to
anything (other than the version diff)? I have another patch from Trond to
apply to the initscript, and more testing would be nice.
No changes
As a general rule I don't. But I'm having a hard time trying to find
out if there is a lock on a given item without attempting to lock it.
Seems to work that way with all locks but most delay until it can
obtain it. Userlocks don't wait.
--
Rod Taylor
BarChord Entertainment Inc.
-
Rod Taylor [EMAIL PROTECTED] writes:
Fiddling with userlock stuff for the purposes of setting up an action
queue. Having the lock in the where clause causes the lock code to
actually lock 2 rows, not just the one that is being returned.
A WHERE clause should *never* contain function calls
On Tue, 8 May 2001, Tom Lane wrote:
Kovacs Zoltan [EMAIL PROTECTED] writes:
I cannot decide if this is a serious bug or not --- some queries from
complex views may give strange results. The next few days I will try to
find the point where the problem is but now I can only include the data
Kovacs Zoltan [EMAIL PROTECTED] writes:
Thanks in advance. Zoltan
You're welcome ;-)
regards, tom lane
*** src/backend/executor/nodeAppend.c.orig Thu Mar 22 01:16:12 2001
--- src/backend/executor/nodeAppend.c Tue May 8 15:48:02 2001
***
*** 8,14
2. The allocation time for raw devices is by far better (near
instantaneous) than creating preallocated files in a
fs. Providing 1 Tb of raw devices is a task of minutes,
creating 1 Tb filsystems with preallocated 2 Gb files is a
task of hours at best.
Filesystem
Right now anyone can look in pg_statistic and discover the min/max/most
common values of other people's tables. That's not a lot of info, but
it might still be more than you want them to find out. And the
statistical changes that I'm about to commit will allow a couple dozen
values
From a portability standpoint, I think if we go anywhere, it would be to
write directly into device files representing sections of a disk.
That makes sense to me. On traditional Unices, we could use the raw
character device for a partition (eg /dev/rdsk/* on Solaris),
On Solaris this
Zeugswetter Andreas SB [EMAIL PROTECTED] writes:
How about letting them see all statistics where they have select permission
on the base table (if that is possible with the new permission table) ?
Yeah, I was thinking the same thing. If we restrict the view on the
basis of current_user
Peter Eisentraut [EMAIL PROTECTED] writes:
The query that showed the bug would serve just fine.
Most of the bug reports we get are far too bulky to be appropriate to
add to the regress tests as-is. IMHO anyway.
We do need more extensive regress tests, but I don't think that slapping
Bruce Momjian [EMAIL PROTECTED] writes:
OK, now that we have started 7.2 development, I am going to go through
the outstanding patches and start to apply them or reject them. They
are at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I could use help in identifying which patches are a
Bruce Momjian [EMAIL PROTECTED] writes:
We need to discuss whether we like the %TYPE feature proposed by Ian
Taylor. It seems awfully nonstandard to me, and I'm not sure that the
value is great enough to be worth inventing a nonstandard feature.
ISTM that people don't normally tie functions
Bruce Momjian [EMAIL PROTECTED] writes:
But don't we already have problems with changing functions that use
tables or does this open a new type of problem?
But this feature isn't about functions that use tables internally;
it's about tying the fundamental signature of the function to a table.
On Tue, May 08, 2001 at 05:49:16PM -0400, Tom Lane wrote:
I presume that Ian is not thinking about such a scenario, but only about
using %type in a schema file that he will reload into a freshly created
database each time he edits it. That avoids the issue of whether %type
declarations can
Richard Poole [EMAIL PROTECTED] writes:
How about a feature in psql which would read something like '%type' and
convert it to the appropriate thing before it passed it to the backend?
That's just about what Ian's patch does, only it does it during backend
parsing instead of in the client. It
Still I don't see what you are wanting in the JDBC driver if
PostgreSQL would return UNKNOWN indicating that the backend is not
compiled with MULTIBYTE. Do you want exact the same behavior as prior
7.1 driver? i.e. reading data from the PostgreSQL backend, assume its
encoding default to
Tatsuo Ishii [EMAIL PROTECTED] writes:
Tom also mentioned that it might be possible for the server to support
setting the character set for a database even when multibyte wasn't
enabled. That would then allow clients like jdbc to get a value from
non-multibyte enabled servers that would
26 matches
Mail list logo
