Well, I finally got a good build of 7.1beta3 in the RPM build environment.
Woohoo.
Most regression tests pass -- 10 of 76 fail in serial mode. I'll be analyzing
the diffs tomorrow afternoon to see what's going on, then will be tidying up
the RPMset for release. Tidy or no, a release will h
[EMAIL PROTECTED] (Nathan Myers) writes:
>> Instead of a partial row CRC, we could just as well use some other bit
>> of identifying information, say the row OID. ...
> Good. But, wouldn't the TID be more specific?
Uh, the TID *is* the pointer from index to heap. There's no redundancy
that w
mlw <[EMAIL PROTECTED]> writes:
> Take this update:
> update table set field = 'X' ;
> This is a very expensive function when the table has millions of rows,
> it takes over an hour. If I dump the database, and process the data with
> perl, then reload the data, it takes minutes. Most of the
* mlw <[EMAIL PROTECTED]> [010113 19:37] wrote:
> Alfred Perlstein wrote:
> >
> > * mlw <[EMAIL PROTECTED]> [010113 17:19] wrote:
> > > I have a question about Postgres:
> > >
> > > Take this update:
> > > update table set field = 'X' ;
> > >
> > >
> > > This is a very expensive function wh
Alfred Perlstein wrote:
>
> * mlw <[EMAIL PROTECTED]> [010113 17:19] wrote:
> > I have a question about Postgres:
> >
> > Take this update:
> > update table set field = 'X' ;
> >
> >
> > This is a very expensive function when the table has millions of rows,
> > it takes over an hour. If I d
* mlw <[EMAIL PROTECTED]> [010113 17:19] wrote:
> I have a question about Postgres:
>
> Take this update:
> update table set field = 'X' ;
>
>
> This is a very expensive function when the table has millions of rows,
> it takes over an hour. If I dump the database, and process the data wit
[EMAIL PROTECTED] writes:
> I am sorry I wasn't listening -- I may have helped by at least
> answering the direct questions and by testing. I have, in fact,
> positively tested both my and Oleg's code in the today's snapshot on a
> number of linux and FreeBSD systems. I failed on this one:
> SunO
On Sat, 13 Jan 2001, Thomas Lockhart wrote:
> > It's pretty dramatic to get the 'You don't have permissions to install'
> > message from the perl 'make install' when I am performing the build (and
> I have been having trouble with one of the package files disappearing
> from the temporary instlla
I have a question about Postgres:
Take this update:
update table set field = 'X' ;
This is a very expensive function when the table has millions of rows,
it takes over an hour. If I dump the database, and process the data with
perl, then reload the data, it takes minutes. Most of the ti
On Sunday 14 January 2001 04:49, Tom Lane wrote:
> A row-level CRC might be useful for this, but it would have to be on
> the data only (not the tuple commit-status bits). It'd be totally
> impractical with a block CRC, I think. To do it with a block CRC, every
> time you changed *anything* in
On Sat, Jan 13, 2001 at 12:49:34PM -0500, Tom Lane wrote:
> [EMAIL PROTECTED] (Nathan Myers) writes:
> > ... for systems that cannot provide strict write ordering (e.g.,
> > most PCs) it would be helpful to be able to detect that the database
> > has become corrupted. In Vadim's example above,
Hi.
Dos any one know any sql sentence to Find primary
keys in a table.
I'm using postgresql v.7.0 (Mandrake
7.2)
I am sorry I wasn't listening -- I may have helped by at least
answering the direct questions and by testing. I have, in fact,
positively tested both my and Oleg's code in the today's snapshot on a
number of linux and FreeBSD systems. I failed on this one:
SunOS typhoon 5.7 Generic_106541-10 sun4
If the year is very large, datetime formatting overflows its limits and
gives very weird results. Either the formatting needs to be improved
or there should be an upper bound on the year.
bray=# select version();
version
---
Hi,
since I have limited bandwidth. Are the diffs between the different versions
available to use with patch instead of always downloading the whole package?
Konstantin
--
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: [EMAIL PROTECTED]
Otkerstr. 28, 81547 Muenchen, Germany. Tel +49 8
[EMAIL PROTECTED] (Nathan Myers) writes:
> To achieve disk write-order independence is probably not a worthwhile
> goal, but for systems that cannot provide strict write ordering (e.g.,
> most PCs) it would be helpful to be able to detect that the database
> has become corrupted. In Vadim's ex
"Len Morgan" <[EMAIL PROTECTED]> writes:
> I have used Postgres and Tcl/Tk for quite some time and yes, when 8.2 came
> out, I had trouble accessing ANYTHING because of the UTF-8 switch. My
> solution was to upgrade my pgsql.tcl file with a new one. I tried it once
> and it worked but other even
> See attached tmpfile.txt...
This distro uses the same or similar compiler flags as does Mandrake,
*and it is the wrong thing to do* The gcc folks recommend against
ever using "-O3" with "-fast-math", but both of these distros do it
anyway.
And you see the results :(
Pick up the .rpmrc I'v
> It's pretty dramatic to get the 'You don't have permissions to install'
> message from the perl 'make install' when I am performing the build (and
> the make install) as root. Particularly when 7.0's perl 'make install'
> worked semi-properly. I say semi-properly because the packing list had
>
> > Oh, not a problem. You're famous for, er, non-verbosity.
> I am. Hmm...
*rofl*
No need to take that as a personal challenge to remove the "non-" from
Lamar's opinion... ;)
- Thomas
> > What I am gathering from all this conversation is that there is no
> > repository for packages.
Whoops. There is a repository for packages on ftp.postgresql.org, and
you are welcome to contribute packages to there. As Peter points out, we
probably aren't helping folks if we have some independ
> ps shows postgresql running:
> /usr/bin/pg_ctl -D /var/lib/pgsql/data -p /usr/bin/postmaster start
> /usr/bin/postmaster -i
> I can poke a hole in my firewall and let you connect to the database if you
> would like troubleshoot my sytem. But I'll need some help setting up
> permissions to allow
FYI...
- Forwarded message from Jordan Hubbard <[EMAIL PROTECTED]> -
From: Jordan Hubbard <[EMAIL PROTECTED]>
Subject: Re: CVS Commit message generator...
Date: Fri, 12 Jan 2001 19:50:33 -0800
Message-ID: <[EMAIL PROTECTED]>
To: Larry Rosenman <[EMAIL PROTECTED]>
Sure, it's all availabl
On Fri, Jan 12, 2001 at 04:38:37PM -0800, Mikheev, Vadim wrote:
> Example.
> 1. Tuple was inserted into index.
> 2. Looking for free buffer bufmgr decides to write index block.
> 3. Following WAL core rule bufmgr first calls XLogFlush() to write
>and fsync log record related to index tuple ins
On Fri, Jan 12, 2001 at 11:30:30PM -0500, Tom Lane wrote:
> >> AFAICS, disk-block CRCs do not guard against mishaps involving intended
> >> writes. They will help guard against data corruption that might creep
> >> in due to outside factors, however.
>
> > Right.
>
> Given that we seem to hav
26 matches
Mail list logo
