Now, Solaris seems to be running all the tests but failing something like
29 out of 85 of them.
With a vanilla ./configure;make, I get this on a make check:
== running regression test queries==
parallel group (13 tests): char int8 oid int2 int4 varchar name boole
On Thu, 21 Nov 2002, Stephan Szabo wrote:
>
> On Thu, 21 Nov 2002, Christopher Kings-Lynne wrote:
>
> > > > > "col" isn't of the general form "indexkey op constant" or "constant op
> > > > > indexkey" which I presume it's looking for given the comments in
> > > > > indxpath.c. I'm not sure what
On Thu, 21 Nov 2002, Christopher Kings-Lynne wrote:
> > > I think his point is that they _should_ be equivalent. Surely there's
> > > something in the optimiser that discards '=true' stuff, like 'a=a'
> should be
> > > discarded?
> >
> > I figure that's what he meant, but it isn't what was said.
On Thu, 21 Nov 2002, Christopher Kings-Lynne wrote:
> > > I think his point is that they _should_ be equivalent. Surely there's
> > > something in the optimiser that discards '=true' stuff, like 'a=a'
> should be
> > > discarded?
> >
> > I figure that's what he meant, but it isn't what was said.
On 21 Nov 2002, Rod Taylor wrote:
> On Thu, 2002-11-21 at 15:09, scott.marlowe wrote:
> > On 21 Nov 2002, Rod Taylor wrote:
> >
> > > On Thu, 2002-11-21 at 14:11, Bruce Momjian wrote:
> > > > Of course, those would be SQL purists who _don'
On 21 Nov 2002, Rod Taylor wrote:
> On Thu, 2002-11-21 at 14:11, Bruce Momjian wrote:
> > Of course, those would be SQL purists who _don't_ understand
> > concurrency issues. ;-)
>
> Or they're the kind that locks the entire table for any given insert.
Isn't that what Bruce just said? ;^)
--
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.
>
On Tue, 12 Nov 2002, Tom Lane wrote:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > OK, make -x check fails, is there some other way to use -x I'm not
> > thinking of here?
>
> I was thinking of running the script by hand, not via make:
>
&
On Tue, 12 Nov 2002, Tom Lane wrote:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > And then it stops. Anyone know why it doesn't run the rest of the
> > regresssion tests?
>
> Somebody else just reported the same thing on Solaris. Must be
&g
On Tue, 12 Nov 2002, Tom Lane wrote:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > And then it stops. Anyone know why it doesn't run the rest of the
> > regresssion tests?
>
> Somebody else just reported the same thing on Solaris. Must be
&g
On 12 Nov 2002, Robert Treat wrote:
> On Tue, 2002-11-12 at 16:27, 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
On 12 Nov 2002, Robert Treat wrote:
> On Tue, 2002-11-12 at 16:27, 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
Curtis, have you considered comparing raw writes versus file system writes
on a raw multi-disk partition?
I always set up my machines to store data on a mirror set (RAID1) or RAID5
set, and it seems your method should be tested there too.
P.s., Tom, the postgresql user would NOT need to run as
On Tue, 12 Nov 2002, Nicolas VERGER wrote:
> Scott you're right, it was a hardware problem.
> Thanks for your help.
>
Glad to be of help. What was the problem? Bad memory or bad hard drive?
Just curious.
---(end of broadcast)---
TIP 6: Have y
On Tue, 5 Nov 2002, Florian Litot wrote:
> what is the command to launch a sql script not in psql
> thanks
without actually being IN psql, you can use it to run one line scripts
like this:
psql dbname -c -- 'single query goes here'
or you can run a large file full of sql queries like this:
ps
I would recommend checking your memory (look for memtest86 online
somewhere. Good tool.) Anytime a machine seems to act flakely there's a
better than even chance it has a bad bit of memory in it.
On Wed, 6 Nov 2002, Nicolas VERGER wrote:
> Hi,
> I have strange stability problems.
> I can't ac
On Thu, 31 Oct 2002, Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > Ok, fair enough -- I agree that we should treat the two cases
> > differently. But one thing I think we should do in any case is improve
> > the wording of the error message.
>
> Got a suggestion?
Change: Relatio
On Tue, 22 Oct 2002, Igor Georgiev wrote:
> > > edit *pg_hba.conf *
> > > # Allow any user on the local system to connect to any
> > > # database under any username, but only via an IP connection:
> > > host all 127.0.0.1 255.255.255.255trust
On 16 Oct 2002, Karl DeBisschop wrote:
> On Mon, 2002-10-14 at 16:14, scott.marlowe wrote:
> > It's on Slashdot, but there's only one post there that mentions the use of
> > Postgresql.
> >
> > On 14 Oct 2002, Robert Treat wrote:
> >
> > > Ye
It's on Slashdot, but there's only one post there that mentions the use of
Postgresql.
On 14 Oct 2002, Robert Treat wrote:
> Yep, that's them. This is a big win from a PostgreSQL advocacy position,
> especially since oracle pr made an official statement against the use of
> PostgreSQL. Has this
On Fri, 11 Oct 2002, Jeff Davis wrote:
> > They also state that they have more sophisticated ALTER TABLE...
> >
> > Only usable feature in their ALTER TABLE that doesn't (yet) exist in
> > PostgreSQL was changing column order (ok, the order by in table creation
> > could be nice), and that's still
Hi Sandeep. What you were calling Hot Backup is really called Point in
Time Recovery (PITR). Hot Backup means making a complete backup of the
database while it is running, something Postgresql has supported for a
very long time.
On Mon, 7 Oct 2002, Sandeep Chadha wrote:
> Hello to all the D
On Fri, 4 Oct 2002, Bruce Momjian wrote:
> Hans-Jürgen Schönig wrote:
> > Did anybody think about threaded sorting so far?
> > Assume an SMP machine. In the case of building an index or in the case
> > of sorting a lot of data there is just one backend working. Therefore
> > just one CPU is use
On Thu, 3 Oct 2002, Manfred Koizar wrote:
> On Wed, 2 Oct 2002 14:07:19 -0600 (MDT), "scott.marlowe"
> <[EMAIL PROTECTED]> wrote:
> >I've found that when the planner misses, sometimes it misses
> >by HUGE amounts on large tables,
>
> Scott,
>
On Thu, 3 Oct 2002, Manfred Koizar wrote:
> On Wed, 2 Oct 2002 14:07:19 -0600 (MDT), "scott.marlowe"
> <[EMAIL PROTECTED]> wrote:
> >I'd certainly be willing to do some testing on my own data with them.
>
> Great!
>
> >Gotta patch?
>
On Wed, 2 Oct 2002, Manfred Koizar wrote:
> As nobody knows how each of these proposals performs in real life
> under different conditions, I suggest to leave the current
> implementation in, add all three algorithms, and supply a GUC variable
> to select a cost function.
I'd certainly be willin
Have you looked at transform_null_equals in the postgresql.conf file to
see if turning that on makes this work like oracle?
On Wed, 2 Oct 2002, Mario Weilguni wrote:
> Ok, I checked this again. Up until 7.2, it was possible to compare an empty string
>to a number, and it worked::
> e.g.: selec
On Tue, 1 Oct 2002, John Liu wrote:
> what's the default lock in pgsql?
>
> if I issued insert(copy)/or update processed
> on the same table but on different records
> the same time, how those processes will
> affect each other?
postgresql does not do "locking" in the sense of how most databas
If you are seeing very slow performance on a drive set, check dmesg to see
if you're getting SCSI bus errors or something similar. If your drives
aren't properly terminated then the performance will suffer a great deal.
---(end of broadcast)---
On Wed, 25 Sep 2002, Jan Wieck wrote:
> "scott.marlowe" wrote:
>
> > Having a FILE called pg_xlog isn't the fix here, it's the result of the
> > fix, which is to take all the steps of moving the pg_xlog directory and
> > put them into one script file
On Wed, 25 Sep 2002, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I don't see the gain of having a file called pg_xlog vs. using GUC.
>
> Well, the point is to have a safety interlock --- but I like Jan's
> idea of using matching identification files in both directories.
> Wit
d, 25 Sep 2002, Bruce Momjian wrote:
>
> I don't see the gain of having a file called pg_xlog vs. using GUC.
>
> ---
>
> scott.marlowe wrote:
> > On Wed, 25 Sep 2002, Curt Sampson wrote:
>
On Wed, 25 Sep 2002, Curt Sampson wrote:
> On Tue, 24 Sep 2002, Jan Wieck wrote:
>
> > And AFAICS it is scary only because screwing that up will simply corrupt
> > your database. Thus, a simple random number (okay, and a timestamp of
> > initdb) in two files, one in $PGDATA and one in $PGXLOG wo
On 19 Sep 2002, Greg Copeland wrote:
> I think Marc made a pretty good case about the use of command line
> arguments but I think I have to vote with Tom. Many of the command line
> arguments you seem to be using do sorta make sense to have for easy
> reference or to help validate your runtime e
I have to say that during beta testing I ALWAYS do an initdb and a reload
just to make sure the pg_dumpall and pg_restore stuff works right. Plus
to make sure problems that might only pop up with a new initdb are found
as well. I probably "burn it to the ground" several times on a single
bet
Hey, me and a few other folks were having a discussion off list, and the
subject of inserts and missing columns came up. you may remember the point
in the "I'm done" post by Bruce. It said:
> o -Disallow missing columns in INSERT ... VALUES, per ANSI
> > What is this, and why is it marked done
On Fri, 13 Sep 2002, Peter Eisentraut wrote:
> Alvaro Herrera writes:
>
> > Is there some documentation on TOAST?
>
> No. Why do you need any?
I think I saw some docs in the
/usr/local/src/postgresql-7.2.1/src/backend/access/heap/tuptoaster.c
file on my box. :-)
Actually it is pretty wel
On Thu, 12 Sep 2002, scott.marlowe wrote:
> Agreed.
>
> Actually, an argument could likely be made that changes that require
> initdb should be done as early as possible since the later the change the
> more people there will be to test the change, and there will be fewe
On Thu, 12 Sep 2002, Matthew T. OConnor wrote:
> > > The count approach seems definitely the right way, but a check (possibly
> > > a slow one) can be probably done without initdb.
> >
> > We can certainly do the proper fix in 7.4; do we consider this bug
> > important enough to do an initdb for
On Fri, 13 Sep 2002, Justin Clift wrote:
> "scott.marlowe" wrote:
>
> > > Seems like the NT4 users are left out in the cold though until we add
> > > some kind of ability for PostgreSQL to not look at the filesystem for
> > > info about where to p
On Thu, 12 Sep 2002, Justin Clift wrote:
> Mike Mascari wrote:
>
> > In Windows 2000 and Windows XP with an NTFS filesystem,
> > Microsoft has added Reparse Points, which allow for the
> > implementation of symbolic links for directories. Microsoft
> > calls them "Junctions". I *believe* the fun
On Tue, 10 Sep 2002, Stephan Szabo wrote:
> On Tue, 10 Sep 2002, scott.marlowe wrote:
>
> > On Tue, 10 Sep 2002, Stephan Szabo wrote:
> >
> > > > > > > It starts a transaction, failes the first command and goes into the
> > > > > > &g
On Tue, 10 Sep 2002, Stephan Szabo wrote:
> > > > > It starts a transaction, failes the first command and goes into the
> > > > > error has occurred in this transaction state. Seems like reasonable
> > > > > behavior.
> > > >
> > > > Select command don't start transaction - it is not good
> > >
On Mon, 9 Sep 2002, Laurette Cisneros wrote:
>
> I am trying move my development database to 7.3b1.
>
> However, when I try to restore from a 7.2.2 dump to the 7.3.b1 server I get
> the following error:
>
> pg_restore -U nbadmin -h lnc -p 5432 -d stats -Fc /tmp/stats.pgdmp
>
> pg_restore: [ar
I'm getting an infinite wait on that file, could someone post it to the
list please?
On Mon, 9 Sep 2002, Bruce Momjian wrote:
>
> OK, turns out that the loop for sequential scan ran fewer times and was
> skewing the numbers. I have a new version at:
>
> ftp://candle.pha.pa.us/pub/pos
On Thu, 5 Sep 2002, Stephan Szabo wrote:
>
> On Thu, 5 Sep 2002, Peter Eisentraut wrote:
>
> > The following happens in latest CVS and a fresh database:
> >
> > create table test (a int);
> > insert into test values (1);
> > alter table test add column b text check (b <> '');
> > alter table te
it to fail, however.
>
> ---
>
> scott.marlowe wrote:
> > Sorry, that should have been:
> >
> > Isn't it true that reindex's behavior ON A FAILURE is to simply, quietly
> > delete the index? t
t; have a reindexdb script.
>
> ---
>
> scott.marlowe wrote:
> > On Tue, 27 Aug 2002, Bruce Momjian wrote:
> >
> > > Christopher Kings-Lynne wrote:
> > > > Would it be worth adding
On Tue, 27 Aug 2002, Bruce Momjian wrote:
> Christopher Kings-Lynne wrote:
> > Would it be worth adding REINDEX ALL and CLUSTER ALL as actual SQL commands?
> > This would be neat. Plus, it means we don't have to worry about having
> > unix-only script in the distro once we have Win32 support.
>
On Tue, 27 Aug 2002, Bruce Momjian wrote:
>
> I had a good chuckle with this. It is the type of "shoot for the moon"
> idea I would have. Maybe I am rubbing off on you. :-)
>
> The only problem I see with this solution is it makes admins think their
> template1 is safe, when it really isn't.
On Mon, 12 Aug 2002, Thomas Lockhart wrote:
> > If you move pg_xlog, you have to create a symlink in /data that points
> > to the new location. Initdb would do that automatically, but if you
> > move it after initdb, you would have to create the symlink yourself.
> > With Thomas's current code,
On Fri, 2 Aug 2002, Thomas Lockhart wrote:
> > > I am wondering why we even want to specify the WAL location anywhere
> > > except as a flag to initdb. If you specify a location at initdb time,
> > > it creates the /xlog directory, then symlinks it into /data.
> > Does this have any negative imp
201 - 252 of 252 matches
Mail list logo
