Re: [HACKERS] Permissions on CHECKPOINT

Tom Lane wrote: >Peter Eisentraut <[EMAIL PROTECTED]> writes: >> Mikheev, Vadim writes: >>> Yes, there should be permission checking - I'll add it later (in 7.1) >>> if no one else. > >> Should be simple enough. Is this okay: > >Actually, I think a more interesting question is "sh

[HACKERS] PQprint

Hi all, Re-posting this to -hackers. Will PQprint() remain/disappear/be replaced in the future? Thx Ed -- ÌĤ¯Ç­¤ÏÁͤòÊá¤é¤Ì

[HACKERS] Minor Sparc/Linux patch (regression test resultmap)....

Just a quick patch to make the geometry test on Sparc/Linux regression tests for Pgsql 7.1beta3 pass. This is very similr to the one I submitted back in July for Linux/Alpha. Apparently non-x86 Linux machines like to compute nth place float point digits like Sun/Solaris does? Othe

Re: [HACKERS] Permissions on CHECKPOINT

Peter Eisentraut <[EMAIL PROTECTED]> writes: > Mikheev, Vadim writes: >> Yes, there should be permission checking - I'll add it later (in 7.1) >> if no one else. > Should be simple enough. Is this okay: Actually, I think a more interesting question is "should CHECKPOINT have permission restrict

Re: [HACKERS] RPM: Contrib request.

Peter Eisentraut <[EMAIL PROTECTED]> writes: >> But, in the instance of pg_dumplo -- can I get some ideas on it? Should >> it be shipped as a separate package, or in the -server subpackage, or?? > It shouldn't be packaged at all because it's not necessary. (pg_dump > dumps large objects.) The

Re: [HACKERS] RPM: Contrib request.

Lamar Owen <[EMAIL PROTECTED]> writes: > I think the cleanest way to provide the contrib programs is to build a > postgresql-contrib with _everything_ in it. >> >> This is what I do for the Debian release. > Precedent set; precedent followed. I'll be hopefully packaging the > _entire_ contrib t

Re: [HACKERS] Open 7.1 items

Sorry for my previous incomplete posting. Peter Eisentraut wrote: > > Bruce Momjian writes: > > > FOREIGN KEY INSERT & UPDATE/DELETE in transaction "change violation" > > You're certainly not going to want to fix this now after having stared at > it for a year? It's not trivial. > What does

Re: [HACKERS] BETWEEN patch

Thomas Swan <[EMAIL PROTECTED]> writes: > select * from foo where fo_num between 1 and 5 > yields the same result as > select * from foo where fo_num between 5 and 1 >> >> This is NOT correct under either SQL92 or SQL99. Read the spec again. > After sending it... I realized that it was not corr

Re: [HACKERS] Open 7.1 items

Peter Eisentraut wrote: > > Bruce Momjian writes: > > > FOREIGN KEY INSERT & UPDATE/DELETE in transaction "change violation" > > You're certainly not going to want to fix this now after having stared at > it for a year? It's not trivial. > What does this item mean ? > > Usernames limited in

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

Frank Joerdens <[EMAIL PROTECTED]> writes: > I just did that and ran make check 4 times. 3 times went completely > smoothly, once I had random fail. This is the same behaviour that I saw > when running make installcheck (76 successful most of the time, > sometimes you get 75 out of 76 with random

Re: [HACKERS] pg_dump issues

At 14:48 24/01/01 -0500, Rod Taylor wrote: >Could we add a flag to remove the postgres specific information from a >pg_dump? It's easy enough to do, but removing all PG-specific information is probably undesirable since, eg, pg_dump does not dump foreign key constraints in a standard way (it just

Re: [HACKERS] RPM: Contrib request.

Oliver Elphick wrote: > > Randy Hall wrote: > >I think the cleanest way to provide the contrib programs is to build a > >postgresql-contrib with _everything_ in it. Those people who need a > >specific binary will be able to get it from /usr/lib/pgsql (or wherever) > >and the distiction b

Re: [HACKERS] RPM: Contrib request.

On Thu, 25 Jan 2001, Lamar Owen wrote: > But, in the instance of pg_dumplo -- can I get some ideas on it? Should > it be shipped as a separate package, or in the -server subpackage, or?? ..ignore it. Not needful for 7.1, but can be interesting for < 7.1 (old DB users can found it directly on

Re: [HACKERS] RPM: Contrib request.

Randy Hall wrote: >I think the cleanest way to provide the contrib programs is to build a >postgresql-contrib with _everything_ in it. Those people who need a >specific binary will be able to get it from /usr/lib/pgsql (or wherever) >and the distiction between core and contrib programs wi

Re: [HACKERS] Open 7.1 items

> Fix for pg_dump of bad system tables Ok. I have made patches for fixing some of pg_dump problems(see attached patches). The patches address the problem with user defined functions, operators and aggregates. Could someone please review and commit them if they look ok? (I'm now in US and have on

Re: [HACKERS] SourceForge & Postgres

Tim Perdue wrote: > I thought the hackers team would be interested in knowing that SourceForge, as > of Friday evening, is running on Postgres. Some 95,000 users and 12,500 Open > Source projects are depending on your stuff, so I hope it's going to be stable > for us. ;-) Tim, the PG core

[HACKERS] Talking about Solaris 7

I have a problem with the compilation of Postgres on Solaris with ssl support. The error I get is this when executing make: gcc -g -Wall -Wmissing-prototypes -Wmissing-declarations -I/usr/local/include -I/usr/local/ssl//include -I../../../src/include -c nodeTidscan.c -o nodeTidscan.ogcc -g -W

Re: [HACKERS] "backend closed" --- I'd like to write a conversionfunction

You probably should be getting core files from this. Have you tried recompiling with debugging and asserts on and then looking through the core file, that might give some more information as to the details. On Thu, 25 Jan 2001, Kovacs Zoltan wrote: > I've got "backend closed" errors --- they s

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report

On Thu, Jan 25, 2001 at 09:47:16PM +0100, Frank Joerdens wrote: > On Thu, Jan 25, 2001 at 12:04:40PM -0800, Ian Lance Taylor wrote: > [ . . . ] > > > for the /tmp directory, which looks distinctly odd to me. What kind of > > > device is swap (I know what swap is normally but I didn't know you coul

[HACKERS] "backend closed" --- I'd like to write a conversion function

I've got "backend closed" errors --- they seem to be indeterministic. I am using 7.0.2 but I tried this with 7.1beta3 as well and the error was similar (but not completely same). I wrote a char* -> char* conversion function. Now I would use textout() and textin() to make it possible using my conv

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

On Thu, Jan 25, 2001 at 12:04:40PM -0800, Ian Lance Taylor wrote: [ . . . ] > > for the /tmp directory, which looks distinctly odd to me. What kind of > > device is swap (I know what swap is normally but I didn't know you could > > mount stuff there . . . )?? > > That is a tmpfs file system which

Re: [HACKERS] RPM: Contrib request.

Now that pg_dump & pg_restore can handle large objects, the only need for pg_dumplo is for migrating large objects from prior versions. I personally cannot see it being used on a day to day basis, but I'm looking at it from a narrow perspective. If it is a separate package, it can easily be remo

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Lookingfor . . . ]

Frank Joerdens writes: > I just typed > > $ mount > > and I get > > /tmp on swap read/write/setuid on Mon Jan 22 16:39:32 2001 That's sufficiently suspicious. Perhaps you could try to change the definition of DEFAULT_PGSOCKET_DIR in src/include/config.h[.in] to something that's on a real disk.

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

Frank Joerdens <[EMAIL PROTECTED]> writes: > I just typed > > $ mount > > and I get > > /tmp on swap read/write/setuid on Mon Jan 22 16:39:32 2001 > > for the /tmp directory, which looks distinctly odd to me. What kind of > device is swap (I know what swap is normally but I didn't know you co

[HACKERS] pg_dump issues

Could we add a flag to remove the postgres specific information from a pg_dump? -- UPDATE "pg_class" SET "reltriggers" = 0 WHERE "relname" ~* 'market_type'; BEGIN TRANSACTION; CREATE TEMP TABLE "tr" ("tmp_relname" name, "tmp_reltriggers" smallint); INSERT INTO "tr" SELECT C."relname", count(T.

Re: [HACKERS] RPM: Contrib request.

Lamar Owen writes: > It has been requested that I ship prebuilt contrib items in the 7.1 > RPMset. Currently, the source code of the whole contrib tree is being > shipped in the main RPM as documentation, It doesn't work to build contrib items without a source tree available. (At least Makefile

Re: [HACKERS] BETWEEN patch

At 1/24/2001 10:19 AM, Tom Lane wrote: >Thomas Swan <[EMAIL PROTECTED]> writes: > > A patch to gram.y in src/backend/parser > > Provides for the SQL99 expected behavior of > > select * from foo where fo_num between 1 and 5 > > yields the same result as > > select * from foo where

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Lookingfor . . . ]

Frank Joerdens writes: > > That's bad, for sure. Maybe you can check for odd conditions surrounding > > the /tmp directory, like is it on NFS, permission problems, mount options. > > I don't have neither root nor physical access to this machine, hence my > options are kinda limited. Entering 'm

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

On Thu, Jan 25, 2001 at 05:12:02PM +0100, Peter Eisentraut wrote: > Frank Joerdens writes: > > > > I have experienced before that Unix sockets will cause random connection > > > abortions on Solaris [ . . . ] > > > > Isn't that _really_ bad? Random connection abortions when going over > > Unix so

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

On Thu, Jan 25, 2001 at 05:12:02PM +0100, Peter Eisentraut wrote: > Frank Joerdens writes: > > > > I have experienced before that Unix sockets will cause random connection > > > abortions on Solaris [ . . . ] > > > > Isn't that _really_ bad? Random connection abortions when going over > > Unix so

[HACKERS] RPM: Contrib request.

It has been requested that I ship prebuilt contrib items in the 7.1 RPMset. Currently, the source code of the whole contrib tree is being shipped in the main RPM as documentation, but only autoinc and refint are being prebuilt (as part of the -test subpackage). I have had three different types o

Re: [HACKERS] postgresql.conf and postgres options

Bruce Momjian writes: > I have added all possible config options to postgresql.conf.sample. It was actually fully intentional that there was *no* list of all possible config options in the sample file, because 1) Who's going to maintain this? 2) People should read the documentation before mess

RE: [HACKERS] Permissions on CHECKPOINT

Mikheev, Vadim writes: > Yes, there should be permission checking - I'll add it later (in 7.1) > if no one else. Should be simple enough. Is this okay: Index: utility.c === RCS file: /home/projects/pgsql/cvsroot/pgsql/src/backend/

[HACKERS] new version of contrib-intarray

Mark, we prepared new version of contrib-intarray - index support for 1-D integer arrays using GiST. Changes: - Improved regression test - Current implementation provides index support for one-dimensional array of int4's - gist__int_ops, suitable for small and medium size of arrays, an

Re: [HACKERS] Open 7.1 items

Bruce Momjian writes: > FOREIGN KEY INSERT & UPDATE/DELETE in transaction "change violation" You're certainly not going to want to fix this now after having stared at it for a year? It's not trivial. > Usernames limited in length Yeah, they are. ;-) If this is referring to pg_passwd, I just

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Lookingfor . . . ]

Frank Joerdens writes: > > I have experienced before that Unix sockets will cause random connection > > abortions on Solaris [ . . . ] > > Isn't that _really_ bad? Random connection abortions when going over > Unix sockets?? My app does _all_ the connecting over Unix sockets?! That's bad, for su

[HACKERS] Re: Re: MySQL has transactions

> When Postgresql 6.5 came out it, it was VERY MUCH better ( many many thanks > to the developers and all involved). And I'm waiting for a solid 7.1 to fix > that <8KB issue. Technically.. <= BLCKSZ (can be up to 32k) I've been using PostgreSQL with a 32k BLCKSZ since 7.0 (on a productions ser

Re: [HACKERS] Re: AW: Re: MySQL and BerkleyDB (fwd)

> yup :-) Maybe this could even be raised to the SQL level, > so applications could use this ? I have not seen this elsewhere, > but why actually not ? Yes please :-) if someone is to code this quicker than me (I suppose so, since I have other projects to deal with concurrently). -- << Tout

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Lookingfor . . . ]

Worked fine for me... % uname -a SunOS lancelot 5.7 Generic_106541-14 sun4m sparc SUNW,SPARCstation-4 % ls -l -rw-r--r-- 1 bpalmer staff32860160 Jan 23 16:45 postgresql-snapshot.tar ... ... ... transactions ... ok random ... failed (ignored) portals

[HACKERS] email address change

My email address has been changed. From now on, please write to [EMAIL PROTECTED] The "tip" user at the same host no longer exists. Sorry for the inconvenience if you tried to send a message to the "tip" user this week. Have a nice day, :^) Zoltan -- Kov\'acs, Zolt\'an

Re: [HACKERS] (one more time) Patches with vacuum fixes available .

> > Did we decide against LAZY? Seems we have a number of people > > concerned about vacuum downtime, and I can see this as a win > > for them. If they don't specify LAZY, the code is not run. > > First sorry that I wasn't able to deal with vlazy earlier. > > Now I have one more open item for 7.1

[HACKERS] Re: PHP - Postgres large object functions

El Mié 24 Ene 2001 17:56, Ned Lilly escribió: > Adam, FYI, according to Rasmus Lerdorf, your patches have been > committed. From the changelog: > > 2001-01-18 Derick Rethans <[EMAIL PROTECTED]> > > > * ext/pgsql/pgsql.c > ext/pgsql/php_pgsql.h: >

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

On Thu, Jan 25, 2001 at 12:42:45AM +0100, Peter Eisentraut wrote: > Frank Joerdens writes: > > [randomly varying set of regression tests fail] > > > Running the tests on my Linux box gives no failed tests. Must I assume > > that those failed tests indicate some issue that is is detrimental to >

Re: [HACKERS] Open 7.1 items

Bruce Momjian <[EMAIL PROTECTED]> writes: > Here are my open 7.1 items. Thanks for shrinking the list so far. > SELECT cash_out(1) crashes all backends This isn't a "must fix for 7.1", any more than it was for 7.0, 6.5, or any other release back to the beginning of time. It's always been possi

Re: [HACKERS] Open 7.1 items

Quoting Bruce Momjian <[EMAIL PROTECTED]>: > I have trickled the emails as I reviewed them, asking for comments. It > was not one big email. I haven't seen them either, although my Inbox is big again, and I'm filtering out mails by their subject line, so it's possible I've missed them. I'm sl

[HACKERS] AW: [HACKERS] WAL documentation

> Using pg_control to get checkpoint position speed up things but > to handle possible pg_control corruption we obviously should > implement reading existent log segments (from the last one - > newest - to oldest) to get last checkpoint. I think this would be *very* important :-) Andreas