On Mon, Mar 12, 2001 at 08:15:02PM +0100, Peter Eisentraut wrote:
> Karel Zak writes:
>
> > > > For transaltion to other languages I not sure with gettext() stuff on
> > > > backend -- IMHO better (faster) solution will postgres system catalog
> > > > with it.
> > >
> > > elog(ERROR, "cannot ope
> Sounds quite unreliable to me. Unless there's some interlock ... like,
> say, the second sync not being able to advance past a buffer page that's
> as yet unwritten by the first sync. But would all Unixen share such a
> strange detail of implementation?
I heard Kirk McKusick tell this story
Tom Lane <[EMAIL PROTECTED]> writes:
> "Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> >> The idea is, that by the time the last sync has run, the
> >> first sync will be done flushing the buffers to disk. - this is what
> >> we were told by the IBM engineers when I worked tier-2/3 AIX support
>
> > Should we try to read log up to the *physical end* - ie end of last
> > log file - regardless invalid CRC-s/zero pages with attempt to
> > re-apply interim valid records? (Or do we already do this?)
>
> That doesn't seem like a good idea --- once we fail to read an XLOG
> record, it's probabl
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
>> The idea is, that by the time the last sync has run, the
>> first sync will be done flushing the buffers to disk. - this is what
>> we were told by the IBM engineers when I worked tier-2/3 AIX support
>> at IBM.
> I was told the same a long ago abo
> > to re-write smgr. I don't know how useful is second sync() call, but
> > on Solaris (and I believe on many other *NIXes) rc0 calls it
> > three times, -:) Why?
>
> The idea is, that by the time the last sync has run, the
> first sync will be done flushing the buffers to disk. - this is what
On Mon, 12 Mar 2001, Mikheev, Vadim wrote:
> to re-write smgr. I don't know how useful is second sync() call, but
> on Solaris (and I believe on many other *NIXes) rc0 calls it
> three times, -:) Why?
The idea is, that by the time the last sync has run, the first sync will
be done flushing the b
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> Maybe now, with two checkpoints in log, we should start redo from
> oldest one? This will increase recovery time of course -:(
Yeah, and it doesn't even solve the problem: consider a crash just
after we've written a shutdown checkpoint record. On re
> The more I think about this, the more disturbed I get. It seems clear
> that this sequence is capable of writing out the checkpoint record
> before all dirty data pages have reached disk. If we suffer a crash
> before the data pages do reach disk, then on restart we will
> not realize we need
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> This code was from the old days when there was no CRC in log records.
Ah, right. The CRC makes things safer ... but there's still a risk
that old log pages could look like a valid continuation.
> Should we try to read log up to the *physical end* -
> I presume the point of this code was that if we recover and
> then suffer
> a later crash at a point where we've just written an xlog record that
> exactly fills an xlog page, a subsequent scan of the log
> might continue
> on from that point and pick up xlog records from the prior (failed)
>
I wrote a couple days ago:
: BTW, can we really trust checkpoint to mean that all data file changes
: are down on disk? I see that the actual implementation of checkpoint is
:
: write out all dirty shmem buffers;
: sync();
: if (IsUnderPostmaster)
: sleep(2);
:
There is another loose end that I forgot I needed to discuss with you.
xlog.c's ReadRecord formerly contained code that would zero out the rest
of the log segment (and delete the next log segment, if any) upon
detecting a missing or corrupted xlog record. I removed that code
because I considered
On Mon, 12 Mar 2001, Tom Lane wrote:
> Ryan Kirkpatrick <[EMAIL PROTECTED]> writes:
> > While testing some existing database applications on 7.1beta4 on
> > my Sparc 20 running Debian GNU/Linux 2.2, I got the following error on
> > attempting to do a vacuum of a table:
>
> > NOTICE: FlushRe
> > A solution is use number based dates without names :-(
> ISO has published a standard on date/time formats, ISO 8601.
> Dates look like "2001-03-22". Times look like "12:47:63".
> The only unfortunate feature is their standard format for a
> date/time: "2001-03-22T12:47:63". To me the ISO d
At 13:34 12/03/01 -0800, Alfred Perlstein wrote:
>Is it possible
>to have a spinlock over it so that an external utility can take a snapshot
>of it with the spinlock held?
I'd suggest that locking the stats area might be a bad idea; there is only
one writer for each backend-specific chunk, and it
On Mon, 12 Mar 2001, Tom Lane wrote:
> >> if this is the case, can we look at applying that patch
> >> tonight, give ppl till Friday to test and put out a RC1
> >> depending on the results?
>
> Patch committed. There are still some loose ends to clean up:
>
> * I need to finish making an xlog-re
>> if this is the case, can we look at applying that patch
>> tonight, give ppl till Friday to test and put out a RC1
>> depending on the results?
Patch committed. There are still some loose ends to clean up:
* I need to finish making an xlog-reset utility for contrib.
* I stubbed out shmctl(
* Bruce Momjian <[EMAIL PROTECTED]> [010312 12:12] wrote:
> I was going to implement the signal handler like we do with Cancel,
> where the signal sets a flag and we check the status of the flag in
> various _safe_ places.
>
> Can anyone think of a better way to get information out of a backend?
Hi,
i've tried to fetch a TIMESTAMP column from the database into a Java
Timestamp instance using the ResultSet.getTimestamp(int index) method.
Whenever i call this method i get some error message:
User.findUser: Bad Timestamp Format at 19 in 2001-03-19 22:05:50.45+01
Bad Timestamp Forma
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> After further research, I remembered that we used to have "DB_MIN
> check" in configure back to 6.4.2:
> I don't know wht it was removed,
Hmm. Digging in the CVS logs shows that it was removed by Bruce in
configure.in version 1.262, 1999/07/18, with the
hi,
I an using postgresql-7.1beta4 and am trying to use the large text fields.
I have heard of TOAST. There is little documentation.
I found one section about creating a data type,
then creating two functions to convert the data types.
Is this how TOAST is implemented?
Am I on the right track?
Please forgive me if I'm misunderstanding something of these rather
complex issues. But I think this is an important question from the
perspective of a sytem administrator responsible for the safety and
uncorruptedness of his users' data.
If I understand correctly, it is possible, through power
[ Charset KOI8-R unsupported, converting... ]
> On Wednesday 07 March 2001 21:56, Bruce Momjian wrote:
> > I have started coding a PostgreSQL performance monitor. It will be like
> > top, but allow you to click on a backend to see additional information.
> >
> > It will be written in Tcl/Tk. I m
Greetings,
Sorry about all the posts lately, but things seems to be running *really*
slow on my database. I have two tables, both are identical and one is used
to hold entries older than a certain date, i.e. the history table. I use
this query to move the old records from one to the other.
> At the end of backend/utils/adt/datetime.c, there is some fairly ugly
> code that is conditionally compiled on
>
> #if defined(linux) && defined(__powerpc__)
>
> Do we still need this? The standard versions of TIMESTAMP_IS_CURRENT
> and TIMESTAMP_IS_EPOCH appear to work just fine on my Powerb
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> I have tested PostgreSQL with 2-4 CPU linux boxes. In summary, 2 CPU
> was a big win, but 4 was not. I'm not sure where the bottle neck is
> though.
Our not-very-good implementation of spin locking (using select() to
wait) might have something to do with
Sorry for taking so long to reply...
On Wed, Mar 07, 2001 at 01:27:34PM -0800, Mikheev, Vadim wrote:
> Nathan wrote:
> > It is possible to build a logging system so that you mostly don't care
> > when the data blocks get written
[after being changed, as long as they get written by an fsync];
> I am looking to beef up a PostgreSQL database by moving it to a Sun
> Enterprise or an Alpha ES-40 or some other multi-CPU platform. My
> questions are;
>
> - What suggestions do people have for a good PostgreSQL platform.
> - How well does PostgreSQLtake advantage of multiple CPUs?
I hav
> > but it's hard to notice eg misprints in 44K file -:)
> > I think we should apply patches and hard test
> > recovering for a few days (power off/pg_ctl -m i stop
> > with dozens update transactions).
>
> if this is the case, can we look at applying that patch
> tonight, give ppl till Friday t
>> > It is possible to build a logging system so that you
>> > mostly don't care when the data blocks get written;
>> > a particular data block on disk is considered garbage
>> > until the next checkpoint, so that you
>> >
> > How to know if a particular data page was modified if there is no
> >
On Mon, 12 Mar 2001, Mikheev, Vadim wrote:
> but it's hard to notice eg misprints in 44K file -:)
> I think we should apply patches and hard test
> recovering for a few days (power off/pg_ctl -m i stop
> with dozens update transactions).
if this is the case, can we look at applying that patch to
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> but it's hard to notice eg misprints in 44K file -:)
> I think we should apply patches and hard test
> recovering for a few days (power off/pg_ctl -m i stop
> with dozens update transactions).
OK. I haven't finished putting together an xlog-reset ut
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> Probably we should update XLogWrite to write() more than 1 block,
> but Tom should apply his patches first (btw, did you implement
> "log file size" condition for checkpoints, Tom?).
Yes I did. There's a variable now to specify a checkpoint every N
> > FSYNC:257tps
> > O_DSYNC: 333tps
> >
> > Just(?) 30% faster, -:(
>
> First of all, if you ask me, that is one hell of an improvement :-)
Of course -:) But tfsync tests were more promising -:)
Probably we should update XLogWrite to write() more than 1 block,
but Tom should ap
but it's hard to notice eg misprints in 44K file -:)
I think we should apply patches and hard test
recovering for a few days (power off/pg_ctl -m i stop
with dozens update transactions).
Vadim
---(end of broadcast)---
TIP 6: Have you searched our l
On Mon, Mar 05, 2001 at 02:00:59PM -0500, Tom Lane wrote:
> [EMAIL PROTECTED] (Nathan Myers) writes:
> > The CRC-64 code used in the SWISS-PROT genetic database is (now) at:
> > ftp://ftp.ebi.ac.uk/pub/software/swissprot/Swissknife/old/SPcrc.tar.gz
>
> > From the README:
>
> > The code
Hi Philip,
I have not updated from CVS in a few days, but I suspect you haven't
noticed this yet: given a mixed-case table name and a scenario that
requires emitting UPDATE pg_class commands, pg_dump puts out
things like
UPDATE "pg_class" SET "reltriggers" = 0 WHERE "relname" ~* '"Table"';
BEGI
Peter Eisentraut writes:
> Michal Maru¹ka writes:
> > What about (optionally) printing the type of the column data?
> >io | tu | tipo |data
> >int | int | int2 |date
> > +---+--+
> > 102242 | 26404 | 1203 | 2000-11-22
> > (1 row)
> I've b
On Mon, Mar 12, 2001 at 11:11:46AM +0100, Karel Zak wrote:
> On Fri, Mar 09, 2001 at 10:58:02PM +0100, Kaare Rasmussen wrote:
> > Now you're talking about i18n, maybe someone could think about input and
> > output of dates in local language.
> >
> > As fas as I can tell, PostgreSQL will only use
On Mon, Mar 12, 2001 at 08:05:26PM +, Peter Mount wrote:
> At 11:41 12/03/01 -0500, Vince Vielhaber wrote:
> >On Mon, 12 Mar 2001, Peter Mount wrote:
> >
> > > Bottom of every page (part of the template) is both my name and email
> > > address ;-)
> >
> >Can we slightly enlarge the font?
>
>
On Wednesday 07 March 2001 21:56, Bruce Momjian wrote:
> I have started coding a PostgreSQL performance monitor. It will be like
> top, but allow you to click on a backend to see additional information.
>
> It will be written in Tcl/Tk. I may ask to add something to 7.1 so when
> a backend recei
""Mikheev, Vadim"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > It is possible to build a logging system so that you mostly don't care
> > when the data blocks get written; a particular data block on disk is
> > considered garbage until the next checkpoint
On Thu, 8 Mar 2001, Philip Warner wrote:
> At 20:48 7/03/01 +, Oliver Elphick wrote:
> >kovacsz wrote:
> > >
> > >You answered that noone experienced anything like this. Here I get this
> > >behaviour with the most simple table as well.
> >
>
> Is there a problem with the lists? I reveive
On Mon, 12 Mar 2001, Peter Mount wrote:
> At 11:41 12/03/01 -0500, Vince Vielhaber wrote:
> >On Mon, 12 Mar 2001, Peter Mount wrote:
> >
> > > Bottom of every page (part of the template) is both my name and email
> > > address ;-)
> >
> >Can we slightly enlarge the font?
>
> Can do. What size do
On 2001.03.07 22:06 Bruce Momjian wrote:
> > I think Bruce wants per-backend data, and this approach would seem to
> only
> > get the data for the current backend.
> >
> > Also, I really don't like the proposal to write files to /tmp. If we
> want a
> > perf tool, then we need to have something
At 12:37 07/03/01 +1100, John Reid wrote:
>Hi,
>
>This was mentioned a while back on this list (pg hackers) - thanks to whoever
>provided the pointer :-) I have not yet looked at it in depth, though
>that is high
>on my list of TO-DO's. It is released under an apache style licence. Any
>reason
On Thu, Mar 08, 2001 at 07:50:15AM -0500, D'Arcy J.M. Cain wrote:
> I am looking to beef up a PostgreSQL database by moving it to a Sun
> Enterprise or an Alpha ES-40 or some other multi-CPU platform. My
> questions are;
>
> - What suggestions do people have for a good PostgreSQL platform.
>
hey friends can u give me a master password so that
i can create user in the postgresql.
thanx
Shailendra Kumar
At 11:41 12/03/01 -0500, Vince Vielhaber wrote:
>On Mon, 12 Mar 2001, Peter Mount wrote:
>
> > Bottom of every page (part of the template) is both my name and email
> > address ;-)
>
>Can we slightly enlarge the font?
Can do. What size do you think is best?
I've always used size=1 for that line.
I was going to implement the signal handler like we do with Cancel,
where the signal sets a flag and we check the status of the flag in
various _safe_ places.
Can anyone think of a better way to get information out of a backend?
--
Bruce Momjian| http://candle.pha.pa.
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Patch or otherwise, this approach seems totally unworkable. A signal
>> handler cannot do I/O safely, it cannot look at shared memory safely,
>> it cannot even look at the backend's own internal state safely. How's
>> it going to do any useful status
I am looking to beef up a PostgreSQL database by moving it to a Sun
Enterprise or an Alpha ES-40 or some other multi-CPU platform. My
questions are;
- What suggestions do people have for a good PostgreSQL platform.
- How well does PostgreSQLtake advantage of multiple CPUs?
Thanks.
--
D'Ar
Hi,
This was mentioned a while back on this list (pg hackers) - thanks to whoever
provided the pointer :-) I have not yet looked at it in depth, though that is high
on my list of TO-DO's. It is released under an apache style licence. Any reason
why there are no pointers to it on the PostgreSQL
On Sun, Mar 04, 2001 at 10:01:37AM +0800, xuyifeng allegedly wrote:
> - Original Message -
> From: The Hermit Hacker <[EMAIL PROTECTED]>
> To: Jaruwan Laongmal <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Friday, March 02, 2001 8:04 PM
> Subject: Re: [HACKERS
Karel Zak writes:
> > > For transaltion to other languages I not sure with gettext() stuff on
> > > backend -- IMHO better (faster) solution will postgres system catalog
> > > with it.
> >
> > elog(ERROR, "cannot open message catalog table");
>
> Sure, and what:
>
> elog(ERROR, gettext("can't s
On Mon, 12 Mar 2001, Peter Mount wrote:
> Bottom of every page (part of the template) is both my name and email
> address ;-)
Can we slightly enlarge the font?
Vince.
--
==
Vince Vielhaber -- KA8CSHemail: [EMAIL PROTEC
At 06:11 06/03/01 -0500, Vince Vielhaber wrote:
>This just came to the webmaster mailbox:
Sorry for the delay, busy week...
>---
>Most of the top banner links on http://jdbc.postgresql.org (like
>Documentation, Tutorials, Resources, Development) throw up 404s if
>followed. Thought you ough
At 23:49 08/03/01 +0100, Peter Eisentraut wrote:
>I really feel that translated error messages need to happen soon.
>Managing translated message catalogs can be done easily with available
>APIs. However, translatable messages really require an error code
>mechanism (otherwise it's completely impo
> Ok, I've made changes in xlog.c and run tests: 50 clients inserted
> (int4, text[1-256]) into 50 tables,
> -B 16384, -wal_buffers 256, -wal_files 0.
>
> FSYNC:257tps
> O_DSYNC: 333tps
>
> Just(?) 30% faster, -:(
First of all, if you ask me, that is one hell of an improvement
Ryan Kirkpatrick <[EMAIL PROTECTED]> writes:
> While testing some existing database applications on 7.1beta4 on
> my Sparc 20 running Debian GNU/Linux 2.2, I got the following error on
> attempting to do a vacuum of a table:
> NOTICE: FlushRelationBuffers(jobs, 1399): block 953 is referenc
While testing some existing database applications on 7.1beta4 on
my Sparc 20 running Debian GNU/Linux 2.2, I got the following error on
attempting to do a vacuum of a table:
NOTICE: FlushRelationBuffers(jobs, 1399): block 953 is referenced (private 0, global
1)
ERROR! Can't vacuum tabl
On Fri, Mar 09, 2001 at 10:58:02PM +0100, Kaare Rasmussen wrote:
> Now you're talking about i18n, maybe someone could think about input and
> output of dates in local language.
>
> As fas as I can tell, PostgreSQL will only use English for dates, eg January,
> February and weekdays, Monday, Tuesd
At 08:59 PM 11-03-2001 -0500, Bruce Momjian wrote:
>How about "Connection terminated by administrator", or something like
>that.
I prefer something closer to the truth.
e.g.
"Received SIGTERM, cancelling query and exiting"
(assuming it actually cancels the query).
But maybe I'm weird.
Cheerio,
On Fri, Mar 09, 2001 at 05:57:13PM +0100, Peter Eisentraut wrote:
> Karel Zak writes:
>
> > For transaltion to other languages I not sure with gettext() stuff on
> > backend -- IMHO better (faster) solution will postgres system catalog
> > with it.
>
> elog(ERROR, "cannot open message catalog t
65 matches
Mail list logo
