> I don't mind contributing the script and schema that I used, but one thing
I
> failed to mention in my first post is that the first thing the script does
> is open connections to 256 databases (all on this same machine), and the
> transactions are relatively evenly dispersed among the 256 connec
OK,
I have modifed heap.c so that it won't automatically generate duplicate
constraint names.
I have _not_ compiled this yet, as it's a bit of a pain for me cos I don't
have bison, etc. However, it looks good to me, and if someone else wants to
test it and then maybe think about if the patch is
> >>> Thus I would be happy if getdatabaseencoding() returned 'UNKNOWN' or
> >>> something similar when in fact it doesn't know what the encoding is
> >>> (i.e. when not compiled with multibyte).
> >>
> >
> > Is that ok for Java? I thought Java needs to know the encoding
> > beforehand so that
On Mon, 7 May 2001, Tom Lane wrote:
> Vince Vielhaber <[EMAIL PROTECTED]> writes:
> > Yeah, I got a note from Peter saying it was fixed in 7.1. Silly me, I
> > thought hub was running 7.1, psql must be 7.0.x.
>
> Looks like there's an older psql in your PATH. You could make sure with
> "psql -V
Tom Lane <[EMAIL PROTECTED]> writes:
> Unfortunately "cvs log" isn't all that great about distinguishing
> branches from tags --- it calls 'em all "symbolic names".
Minor addition to this: you can distinguish branches and tags by using
`cvs status -v'.
(Historical note: CVS was originally imple
mlw <[EMAIL PROTECTED]> writes:
> template1=# create database fubar with location = '/tmp' ;
> ERROR: CREATE DATABASE: could not link '/postgres/data/base/12523613' to
> '/tmp/base/12523613': Operation not permitted
Try using a filesystem that supports symbolic links ...
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Sounds fine, but aren't most people who we ask for stats superusers?
Are they? I don't think we should assume that.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get
Philip Warner <[EMAIL PROTECTED]> writes:
> At 11:22 7/05/01 -0400, Tom Lane wrote:
>> Do you need a quick lecture on CVS branch management?
> That would be sensible.
OK, some quick notes for those with commit privileges:
If you just do basic "cvs checkout", "cvs update", "cvs commit", then
you
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> It seems to me that only superusers should be allowed to read the
>> pg_statistic table. Or am I overreacting? Comments?
> You are not overreacting. Imagine a salary column. I can imagine
> max/min being quite interesting.
A fine example, indeed ;
At 11:22 7/05/01 -0400, Tom Lane wrote:
>
>Do you need a quick lecture on CVS branch management?
>
That would be sensible.
Philip Warner| __---_
Albatross Consulting Pty. Ltd. |/ - \
(A.B.N
Hello, All
How I prevent a new user to create new tables in a Data Base ?
The Data Base is owned by "postgres" and I need that only the "postgres"
user can create new tables ...
---
Where are the default messages thats appears when the Referentian
Integrity is violated ? I need change thi
> takes Vince a day or two to catch up ... yes, we are officially released,
> and Tom just dump'd some major stats changes into HEAD ...
>
> On Mon, 7 May 2001, Tatsuo Ishii wrote:
>
> > Does this mean that we have officially released 7.1.1? I could not
> > find any statements regarding 7.1.1 o
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can someone remind me what we are going to do with this?
I'd like to see some effort put into implementing the SQL-standard
privilege model, rather than adding yet more ad-hoc user properties.
The more of these we make, the more painful it's going to be
[EMAIL PROTECTED] (Trond Eivind Glomsrød) writes:
> "Ken Hirsch" <[EMAIL PROTECTED]> writes:
>
> > I don't have a machine with XFS installed and it will be at least a week
> > before I could get around to a build. Any volunteers?
>
> I think I could do that... any useful benchmarks to run?
In
Lieven Van Acker <[EMAIL PROTECTED]> writes:
> Are the "nested views permission problems" fixed in this release?
> If so, a dump IS necessary because of a change rule creation routines.
If you're running into that issue, you might want to drop and recreate
the affected views/rules. That's a far
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> Yeah, I got a note from Peter saying it was fixed in 7.1. Silly me, I
> thought hub was running 7.1, psql must be 7.0.x.
Looks like there's an older psql in your PATH. You could make sure with
"psql -V".
regards, tom lane
-
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can someone explain why we have a lisp.sgml file in our docs? Seems it
> descripes a 3rd party Emacs interface. I don't think we should start
> distributing docs for software we don't distribute. Can I remove it?
Only if you move the pointer to somep
Doug McNaught wrote:
>
> That makes sense to me. On "traditional" Unices, we could use the raw
> character device for a partition (eg /dev/rdsk/* on Solaris), and on
> Linux we'd use /dev/raw*, which is a mapping to a specific partition
> established before PG startup.
Small update - newer Linu
Bruce Momjian <[EMAIL PROTECTED]> writes:
> That is a major issue for people running performance tests. For
> example, XFS may be slow on 2.2 kernels but not 2.4 kernels.
XFS is 2.4 only, AFAIK - even the installer modifications SGI did to
Red Hat Linux 7 (which is shipped with a 2.2 kernel) in
On Mon, 7 May 2001, Bruce Momjian wrote:
> > postgresql=> \h create table
> > Command: CREATE TABLE
> > Description: Creates a new table
> > Syntax:
> > CREATE [ TEMPORARY | TEMP ] TABLE table (
> > column type
> > [ NULL | NOT NULL ] [ UNIQUE ] [ DEFAULT value ]
> > [column_const
Tom Lane <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> > If you're using raw devices on Linux and get a win there, it's a win
> > for Postgresql on Linux. ...
> > It all comes down to if it actually would give a performance boost,
> > how muc
Hi,
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 which don't give the correct result. A
lot
Tom Lane wrote:
> "Serguei Mokhov" <[EMAIL PROTECTED]> writes:
> > Being a simple user, I still want to view the stats from the table,
> > but it should be limited only to the stuff I own. I don't wanna let
> > others see any of my info, however. The SU's, of course, should be
> > able to read al
On Mon, 7 May 2001, Bruce Momjian wrote:
> > postgresql=> \h create table
> > Command: CREATE TABLE
> > Description: Creates a new table
> > Syntax:
> > CREATE [ TEMPORARY | TEMP ] TABLE table (
> > column type
> > [ NULL | NOT NULL ] [ UNIQUE ] [ DEFAULT value ]
> > [column_const
[EMAIL PROTECTED] (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> If you're using raw devices on Linux and get a win there, it's a win
> for Postgresql on Linux. ...
> It all comes down to if it actually would give a performance boost,
> how much work it is and if someone wants to do it.
No,
Philip Warner <[EMAIL PROTECTED]> writes:
> The attached patch should fix the problem. Assuming it tests out OK, can
> this be back-patched, since 7.1.1 is already out?
Yes, it should be back-patched into the REL7_1_STABLE branch once you're
confident of it. Probably there will be a 7.1.2 by and
On Mon, 7 May 2001, The Hermit Hacker wrote:
>
> takes Vince a day or two to catch up ... yes, we are officially released,
> and Tom just dump'd some major stats changes into HEAD ...
But this time Vince had all the info online in a matter of minutes
after receiving Marc's announcement. It does
Marko Kreen <[EMAIL PROTECTED]> writes:
> On Sat, May 05, 2001 at 10:10:33PM -0400, mlw wrote:
> > I think it is simpler problem than that. Postgres, with fsync enabled, does a
> > lot of work trying to maintain data integrity. It is logical to conclude that a
> > file system that does as little
>>> Really? We are removing usesysid? Seems the admin will no longer be
>>> able to choose the users id, right?
>>
>> Not that this was ever useful.
> Except for re-adding users.
Yes. In theory, the correct answer to that is to add referential
integrity checks that prevent you from dropp
> > I don't have a machine with XFS installed and it will be at least a week
> > before I could get around to a build. Any volunteers?
>
> I think I could do that... any useful benchmarks to run?
Looks like we have expert help here :-) One very interesting question
would imho be, how do we bes
I have run a simple PostgreSQL benchmark on my SGI system which uses
XFS for its file system on all disks to compare the effect of fsync.
The benchmark was the loading of a database from 157 MB of pg_dump data
including the construction of 11 Btree indexes covering nearly all
of the data. The seco
At 23:04 7/05/01 +1000, Philip Warner wrote:
>
>It's actually a more general problem - it looks like dumping views in 7.0
>does not work with the 7.1.1 pg_dump (it thinks they are tables because the
>7.1 check of pg_relkind='v' is not valid).
>
The attached patch should fix the problem. Assuming
PHP users tend to start with MySQL and stick there.
PostgreSQL from release 7 is getting rave reviews for being equivalent
in performance to MySQL in medium size web sites.
Perhaps it is time for PHP programmers to dive straight in to
postgreSQL.
Wanted:
PostgreSQL expert to rave about PostgreSQ
At 13:19 7/05/01 +0300, Alessio Bragadini wrote:
>
>Seems that there is a problem dumping 'INSERT-style' from a 7.0.X
>database.
>
It's actually a more general problem - it looks like dumping views in 7.0
does not work with the 7.1.1 pg_dump (it thinks they are tables because the
7.1 check of pg_
takes Vince a day or two to catch up ... yes, we are officially released,
and Tom just dump'd some major stats changes into HEAD ...
On Mon, 7 May 2001, Tatsuo Ishii wrote:
> Does this mean that we have officially released 7.1.1? I could not
> find any statements regarding 7.1.1 on the web pag
Does this mean that we have officially released 7.1.1? I could not
find any statements regarding 7.1.1 on the web pages...
--
Tatsuo Ishii
> This is just a quick announcement that we have now branched off v7.1.x
> from the main development tree, and are starting to dive into development
> of v7.
I've tried the pg_dump bundled in the new 7.1.1 release. I wanted to
test its feature of dumping a 7.0.X database.
Let's say I have database A running 7.1.1, B running 7.0.2. Both servers
have the same database 'test', 'myview' is a view defined on both of
them. I want to dump data only, being a
> > I think it's worth noting that Oracle has been petitioning the
> > kernel developers for better raw device support: in other words,
> > the ability to write directly to the hard disk and bypassing the
> > filesystem all together.
>
> But there could be other reasons why Oracle would want
38 matches
Mail list logo
