On Thu, 2 Nov 2000 [EMAIL PROTECTED] wrote:
> >> I too got somehow on the list without subscribing.
> >> Something is wrong. But I
> >> like it and will stay on. :)
>
> > Marc, not sure what you are doing over there with the
> > mailing lists, but
> > keep it up. :-)
>
> Hmmm! What happened to t
Bruce Momjian writes:
> I have marked 7.0.3 release tree. The new 7.0.3 items are listed
> below.
So have Jason's patches to build on Cygwin not made it in?
On a related note, what tag should I give to cvs to get code from the
7.0.3 branch? Is it REL7_0_PATCHES?
--
Pete Forman
>so, what have you tried to do to set it as digest, and what error did you
get?
I had been getting digests up until about a week or so ago. I assumed
something might have changed with the list server so I submitted a request
for a digest, but keep getting individual e-mails.
My request was sent
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
>
> > BTW,I sometimes see
> > ERROR: SearchSysCache: recursive use of cache 10(16)
> > under small MAXNUMMESSAGES environment.
> > I'm not sure about the cause but suspicious if sufficiently
> > many system relations are
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
>
> "Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> > Doesn't current heap_open() have a flaw that even the first
> > use of a relation in a transaction may cause an error
> > "relation ### modified while in use" ?
>
> Sure,
> > The problem at hand is that
> > a plan may be invalidated before it is even finished building. Do you
> > expect the parse-rewrite-plan-execute pipeline to be prepared to back up
> > and restart if we notice a relation schema change report halfway down the
> > process?
Yes, during the proce
Hi Bruce, Hi Michael,
here is the really short patch for shutting out all postgres definitions
from ecpg
programs. (e.g. Datum, Pointer, DEBUG, ERROR).
Someone really should take a look into libpq and do the same.
But I had to copy a small part of c.h (bool,true,false,TRUE,FALSE) into
ecpg/includ
I agree with leaving it be in contrib. The lesson has been learned,
and contrib has certainly gone out in _much_ worse shape, with code that
wouldn't even compile.
Ross
--
Open source code is like a natural resource, it's the result of providing
food and sunshine to programmers, and then staying
Denis Perchine wrote:
> Hello,
>
> Having some expirience with catching errors with BLOBs, I realised, that it
> is really hard to understand that you forget to enclose BLOB operations in
> transaction...
>
> I would like to add a check for each BLOB operation which will check whether
> we are in
Karel Zak wrote:
> On Thu, 2 Nov 2000, Zeugswetter Andreas SB wrote:
>
> >
> > > Well I can re-write and resubmit this patch. Add it as a
> > > compile time option
> > > is not bad idea. Second possibility is distribute it as patch
> > > in the contrib
> > > tree. And if it until not good tested
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
>> Right. So what do you think about a hint that takes the form of a SET
>> variable for the fetch percentage to assume for a DECLARE CURSOR?
> Since we don't have other hints that are embedded directly into the SQL
> that sounds perfect.
> Th
I wrote:
> Denis Perchine <[EMAIL PROTECTED]> writes:
>> When I run 2 vacuum's in parallel they hangs. Both.
>> I use PostgreSQL from 7.0.x CVS (almost 7.0.3).
> Hm. I don't see a hang, but I do see errors like
> NOTICE: Deadlock detected -- See the lock(l) manual page for a possible cause.
>
Hi,
I start yesterday CVS PostgreSQL server, and saw strange thing:
from user postgres:
# create database test;
CREATE
# \c test;
#create user bobson with password '1' nocreatedb nocreateuser;
CREATE
#create table a (a int4);
CREATE
#revoke all on a from public;
CHANGE
and now from user bobson a
Partyka Robert <[EMAIL PROTECTED]> writes:
> #create user bobson with password '1' nocreatedb nocreateuser;
> CREATE
> #create table a (a int4);
> CREATE
> #revoke all on a from public;
> CHANGE
> and now from user bobson after conecting to test database:
> #insert into a values ('1');
> INSERT 19
> Partyka Robert <[EMAIL PROTECTED]> writes:
> > #create user bobson with password '1' nocreatedb nocreateuser;
> > CREATE
> > #create table a (a int4);
> > CREATE
> > #revoke all on a from public;
> > CHANGE
> > and now from user bobson after conecting to test database:
> > #insert into a values
I was installing the snapshot version last night, whenever I
initialized the database with "initdb -E EUC_TW -D
/usr/local/pgsql/data", I got error message that the EUC_TW was not
the valid encoding. Is it a bug in the snapshot version?
Thanks
Dave
Forwarded from Mosix mailing-list.
Is this a crazy stuff?
Mosix isn't useful for shared memory processes (like apache and postgresql)
it simply doesn't migrate such tasks.
You can do a simple connect script that , for example , do a
round-robin connection to the different postgresql servers on t
I wrote:
> Oops. Strange though, this looks like it must be a very long-standing
> bug: aclinsert3 thinks it can delete any zero-permissions item from an
> ACL array, whereas aclcheck has a hard-wired assumption that the world
> item is always there. Could we have missed this for this long?
Yup
Partyka Robert <[EMAIL PROTECTED]> writes:
> if I do
> # grant UPDATE, INSERT, SELECT on a to user1;
> it was treat as:
> # grant UPDATE, INSERT, DELETE, SELECT on a to user1;
Yeah. The underlying permission set is actually "read, write, append"
(where write access also allows append). So UPDA
* Larry Rosenman <[EMAIL PROTECTED]> [001028 02:23]:
> I don't think we need this ASAP for 7.1. Let's get the basic stuff
> working from a "least surprise" standpoint, and see what the user base
> comes up with. I really think your proposal from earlier tonite is
> the way to go, at least from m
Larry Rosenman <[EMAIL PROTECTED]> writes:
> What was the final outcome?
I don't think we'd quite agreed what to do. The proposed code changes
are not large, we just need a consensus on what the behavior ought to
be.
Since a couple of people objected to the idea of using casts to control
the ou
Works for me.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
>What's the matter with the website? I can access it
>just fine. Perhaps you're finding a bad mirror site?
>Vince.
After sending a request for "http://www.postgresql.org/", I got this:
"Error 400 - Proxy Error: Host name not recognized or host not found - URL
http://www.404627944.com:81/post
Frank Joerdens <[EMAIL PROTECTED]> writes:
> [ DBD::Pg fails against current sources with ]
> DBD::Pg::db table_info failed: ERROR: Unable to identify an ordering
> operator '<' for type 'unknown'
Hmm. It looks like this is caused by my reimplementation of UNION to
use CASE-style datatype resol
On Fri, 3 Nov 2000 [EMAIL PROTECTED] wrote:
> >What's the matter with the website? I can access it
> >just fine. Perhaps you're finding a bad mirror site?
>
> >Vince.
>
>
> After sending a request for "http://www.postgresql.org/", I got this:
> "Error 400 - Proxy Error: Host name not recognized
Hi
Yeach ... I can revoke from public now ;), but .
look at this:
#create database a
CREATE
#\c a
#create table ala(a int4);
CREATE
#\z
Access permissions for database "a"
Relation | Access permissions
--+
ala |
(1 row)
#revoke all on ala from public;
CHA
We've expended a lot of worry and discussion in the past about what
happens if the OID generator wraps around. However, there is another
4-byte counter in the system: the transaction ID (XID) generator.
While OID wraparound is survivable, if XIDs wrap around then we really
do have a Ragnarok scen
Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
Terminating any active server processes...
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died abnormally and
possibly corrupted shared memory.
I have ro
Partyka Robert <[EMAIL PROTECTED]> writes:
> #create table ala(a int4);
> CREATE
> #\z
> Access permissions for database "a"
> Relation | Access permissions
> --+
> ala |
> (1 row)
> #revoke all on ala from public;
> CHANGE
> #\z
> Access permissions for databa
* Dan Moschuk <[EMAIL PROTECTED]> [001103 14:55] wrote:
>
> Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
> Terminating any active server processes...
> NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend died a
I'm trying to compile the CVS (fresh download) of postgres and I get this
running the configure script:
checking for tzname... yes
checking for union semun... no
checking for struct sockaddr_un... yes
checking for int timezone... yes
checking types of arguments for accept()... configure: error:
Dan Moschuk <[EMAIL PROTECTED]> writes:
> Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
What's signal 26 on your system? (Look in /usr/include/signal.h or
/usr/include/signum.h or /usr/include/sys/signal.h)
regards, tom lane
| > Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
|
| What's signal 26 on your system? (Look in /usr/include/signal.h or
| /usr/include/signum.h or /usr/include/sys/signal.h)
dan@spirit:/home/dan grep 26 /usr/include/sys/signal.h
#define SIGVTALRM 26 /
| > This happens fairly regularly. I assume exit code 26 is used to dictate
| > that a specific error has occured.
| >
| > The database is a decent size (~3M records) with about 4 indexes.
|
| What version of postgresql? Tom Lane recently fixed some severe problems
| with vacuum and heavily u
* Dan Moschuk <[EMAIL PROTECTED]> [001103 15:32] wrote:
>
> | > This happens fairly regularly. I assume exit code 26 is used to dictate
> | > that a specific error has occured.
> | >
> | > The database is a decent size (~3M records) with about 4 indexes.
> |
> | What version of postgresql? To
* Nathan Boeger <[EMAIL PROTECTED]> [001103 15:43] wrote:
> is anyone working on the port of PostgreSQL for Alpha FreeBSD ?? I have
> been waiting for over a year very very patiently !!!
>
> I really love my Alpha FreeBSD box and I want to use PostgreSQL on it...
> but postgresql does not build.
sorry, the migration this past weekend was to remove all traces of hub.org
from the list addresses ... we built a 'virtual server' that now houses
the postgresql.org mailing lists, so you need to send to
[EMAIL PROTECTED], and it should work ...
please try that and let me know if it works or not
Dan Moschuk <[EMAIL PROTECTED]> writes:
> | > Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
> |
> | What's signal 26 on your system?
> #define SIGVTALRM 26 /* virtual time alarm */
Well, that sure shouldn't be happening. You aren't perhaps running it
u
> This comparison will work as long as the range of interesting XIDs
> never exceeds WRAPLIMIT/2. Essentially, we envision the actual value
> of XID as being the low-order bits of a logical XID that always
> increases, and we assume that no extant XID is more than WRAPLIMIT/2
> transactions old,
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> So, we'll have to abort some long running transaction.
Well, yes, some transaction that continues running while ~ 500 million
other transactions come and go might give us trouble. I wasn't really
planning to worry about that case ;-)
> Required fre
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
> I'm trying to compile the CVS (fresh download) of postgres and I get this
> running the configure script:
> checking types of arguments for accept()... configure: error: could not
> determine argument types
Hm, how do your system's include fil
I don't think Dan's problem is related to the recently found VACUUM
bugs. Killing a backend with SIGVTALRM suggests that something thinks
the backend's been running too long. ulimit is a likely suspect.
Another possibility is some sort of profiling mechanism gone haywire.
There's nothing in our
At 17:47 3/11/00 -0500, Tom Lane wrote:
>* portability --- I don't believe long long int exists on all the
>platforms we support.
Are you sure of this, or is it just a 'last time I looked' statement. If
the latter, it might be worth verifying.
>* performance --- except on true 64-bit platforms,
> I was installing the snapshot version last night, whenever I
> initialized the database with "initdb -E EUC_TW -D
> /usr/local/pgsql/data", I got error message that the EUC_TW was not
> the valid encoding. Is it a bug in the snapshot version?
Sorry, I forgot to add EUC_TW encoding. Should be o
Philip Warner <[EMAIL PROTECTED]> writes:
>> * disk space --- letting pg_log grow without bound isn't a pleasant
>> prospect either.
> Maybe this can be achieved by wrapping XID for the log file only.
How's that going to improve matters? pg_log is ground truth for XIDs;
if you can't distinguish
Can someone tell me if this patch should be applied? Seems like it was
just for testing, right?
> Tom Lane wrote:
> >
> > I have made a first cut at completing integration of Adriaan Joubert's
> > BIT code into the backend. There are a couple little things left to
> > do (for example, scalarlt
Tom Lane wrote:
>
> Philip Warner <[EMAIL PROTECTED]> writes:
> >> * disk space --- letting pg_log grow without bound isn't a pleasant
> >> prospect either.
>
> > Maybe this can be achieved by wrapping XID for the log file only.
>
> How's that going to improve matters? pg_log is ground truth f
Agreed with all of it, but how about incorporating conversion from inet
to int8? (first octet*256*256*256+second octet*256*256+third
octet*256+fourth octet).
This will allow to do a lot of magic with addresses using plain math.
Also, I'd still like netmask_length, length of netmask in bits.
-a
* Alex Pilosov <[EMAIL PROTECTED]> [001103 20:47]:
> Agreed with all of it, but how about incorporating conversion from inet
> to int8? (first octet*256*256*256+second octet*256*256+third
> octet*256+fourth octet).
>
> This will allow to do a lot of magic with addresses using plain math.
>
> Al
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> What part of "no new features in bug-fix releases" is giving people
> trouble?
Interesting observation here: the key developers seem to be much more
exercised about this than the rest of the community. Counting core
members and Peter we have three "
> Bruce Momjian writes:
>
> > OK, we have votes from Lamar, Ned, Jan, and someone else to keep it in
> > /contrib, votes from Marc and Tom to remove it completely.
> >
> > Other votes?
>
> What part of "no new features in bug-fix releases" is giving people
> trouble?
>
> If Great Bridge wants
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > What part of "no new features in bug-fix releases" is giving people
> > trouble?
>
> Interesting observation here: the key developers seem to be much more
> exercised about this than the rest of the community. Counting core
> members and Peter w
> Bruce Momjian writes:
> > I have marked 7.0.3 release tree. The new 7.0.3 items are listed
> > below.
>
> So have Jason's patches to build on Cygwin not made it in?
No, they are too risky for a minor release.
> On a related note, what tag should I give to cvs to get code from the
> 7.0.3 b
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
> I did understand this, but I still disagree. Whether this is what you want
> strongly depends on what the application does with the resulting rows.
Sure ...
> There is no way for the backend to know this, thus imho the app needs
> to give a hi
> > There is no way for the backend to know this, thus imho the app needs
> > to give a hint.
>
> Right. So what do you think about a hint that takes the form of a SET
> variable for the fetch percentage to assume for a DECLARE CURSOR?
Since we don't have other hints that are embedded directl
Nathan Boeger wrote:
> is anyone working on the port of PostgreSQL for Alpha FreeBSD ?? I have
> been waiting for over a year very very patiently !!!
>
> I really love my Alpha FreeBSD box and I want to use PostgreSQL on it...
> but postgresql does not build.
>
> If they need a box I am more tha
is anyone working on the port of PostgreSQL for Alpha FreeBSD ?? I have
been waiting for over a year very very patiently !!!
I really love my Alpha FreeBSD box and I want to use PostgreSQL on it...
but postgresql does not build.
If they need a box I am more than willing to give them complete ac
Got this in my inbox today - might be of interest to some in this
group. I don't know anything about them- forwarding it as interesting
info only. Note: It starts in about an hour!
--
Join us at SearchDatabase.com TODAY, Friday, November 3rd at 11:00
Eastern (16:00 GMT) for a Live Expert Q
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Either that, or convert it to an absolute path. The problem is that the
>> backends chdir() to their individual databases' data directories, so
>> relative paths that were OK from the postmaster's perspective are no
>> good anymor
> With the new oid file naming, the alternative database
> location feature has disappeared. Not good.
>
> Also, is there any merit in keeping the #ifdef
> OLD_FILE_NAMING code path?
No one. I've removed some of old code but not all, sorry.
> I could probably go through and fix this, but I'm
> > I'd say that normally you're not using cursors because you intend to throw
> > away 80% or 90% of the result set, but instead you're using it because
> > it's convenient in your programming environment (e.g., ecpg). There are
> > other ways of getting only some rows, this is not it.
>
> I d
* Peter Eisentraut <[EMAIL PROTECTED]> [001103 16:16] wrote:
> Alfred Perlstein writes:
>
> > Part of the problem is that Postgresql assumes FreeBSD == -m486,
>
> If that's all then go into src/template/freebsd and remove it.
ok, thanks for the pointer, I'll try to have some patches in the
near
Alfred Perlstein writes:
> Part of the problem is that Postgresql assumes FreeBSD == -m486,
If that's all then go into src/template/freebsd and remove it.
The interesting question is whether the spinlock code, which was written
for Alpha/Linux, works (src/include/storage/s_lock.h). All the res
Nathan Boeger <[EMAIL PROTECTED]> writes:
> is anyone working on the port of PostgreSQL for Alpha FreeBSD ??
Not that I know about. DEC/Compaq was kind enough to lend the project
an Alpha for testing, but it's running Linux (RedHat 6.2).
> If they need a box I am more than willing to give them
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> Jeff, feel like trying out the True64 install and seeing how it
> goes? Worst case, we have to install Redhat from scratch *shrug*
> Tom, anything on that machine that you wanna backup? Or its all safe?
No problem for me. Just keep us posted on
On Fri, 3 Nov 2000, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > Jeff, feel like trying out the True64 install and seeing how it
> > goes? Worst case, we have to install Redhat from scratch *shrug*
>
> > Tom, anything on that machine that you wanna backup? Or its all saf
On Fri, 3 Nov 2000, Tom Lane wrote:
> Nathan Boeger <[EMAIL PROTECTED]> writes:
> > is anyone working on the port of PostgreSQL for Alpha FreeBSD ??
>
> Not that I know about. DEC/Compaq was kind enough to lend the project
> an Alpha for testing, but it's running Linux (RedHat 6.2).
We've als
67 matches
Mail list logo
