Re: [HACKERS] PostgreSQL 8.2beta1 w/ VALUES
Luke, et al, * Luke Lonergan ([EMAIL PROTECTED]) wrote: Except that one warning would not be accurate, because the warning is per tuple. How is postgresql going to know that the warning applies to the same set of data but just a different tuple? I didn't say it'd be easy. :) If it's going to roll back the entire load after that one warning, it should terminate there. It didn't terminate it, though I agree that it would have been nice if I could control if it would terminate on first warning or not. This is a common problem with OLAP and based on the observation here, this needs to be fixed. Not being able to cancel out at this point is even worse, can you imagine the frustration of trying to load 10GB of data and having to wait until the end after seeing these warnings, while knowing that you're just going to have to try again anyway? Yes, rather frustrating even with only 20k rows. Eventually we'll implement single row error handling, but even then there should be a selectable behavior to terminate the load on the first warning/error. It'd be nice to be able to do what (I believe..) Oracle and Access can do- dump the warnings/error messages/rows into a seperate table and go over them afterwards.. Probably wouldn't have helped me in this case but I've been in other situations where it would have been nice. :) Thanks, Stephen signature.asc Description: Digital signature
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Alvaro Herrera wrote: On the other hand, I don't understand why DocBook would be Latin-1 only. What would be the point of that limitation? Some googling seems to reveal that people indeed uses other charsets, UTF-8 in particular (but also Big5, Latin-2, etc), so apparently this isn't set in stone. (I admit that they mainly talk about XML Docbook though). DocBook SGML is Latin 1; DocBook XML, like all XML, is UCS-4. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] Buildfarm alarms
-Original Message- From: Andrew Dunstan [mailto:[EMAIL PROTECTED] Sent: 24 September 2006 03:13 To: Dave Page Cc: pgsql-hackers@postgresql.org Subject: Re: Buildfarm alarms It could certainly be done. In general, I have generally taken the view that owners have the responsibility for monitoring their own machines. I'll think about it some more. We are monitoring the machine, however in this case nothing appeared wrong to the monitoring processes - what had happened was that both had hung or got in an inifinite loop in ECPG-check, the machine was running just fine, and a glance at the process list showed everything I'd expect to see during a normal run. A system for detecting lack of reports from a member would definitely have helped in this case. Regards, Dave ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Fwd: Is the fsync() fake on FreeBSD6.1?
Andrew - Supernews wrote: Whether the underlying device lies about the write completion is another matter. All current SCSI disks have WCE enabled by default, which means that they will lie about write completion if FUA was not set in the request, which FreeBSD never sets. (It's not possible to get correct results by having fsync() somehow selectively set FUA, because that would leave previously-completed requests in the cache.) WCE can be disabled on either a temporary or permanent basis by changing the appropriate modepage. It's possible that Linux does this automatically, or sets FUA on all writes, though that would surprise me considerably; however I disclaim any knowledge of Linux internals. The Linux SATA driver author Jeff Garzik suggests [note 1] that The ability of a filesystem or fsync(2) to cause a [FLUSH|SYNC] CACHE command to be generated has only been present in the most recent [as of mid 2005] 2.6.x kernels. See the write barrier stuff that people have been discussing. Furthermore, read-after-write implies nothing at all. The only way to you can be assured that your data has hit the platter is (1) issuing [FLUSH|SYNC] CACHE, or (2) using FUA-style disk commands It sounds like your test (or reasoning) is invalid. Before those min-2005 2.6.x kernels apparently fsync on linux didn't really try to flush caches even when drives supported it (which apparently most actually do if the requests are actually sent). [note 1] http://lkml.org/lkml/2005/5/15/82 ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] PostgreSQL 8.2beta1 w/ VALUES
Hi, Luke, Luke Lonergan wrote: If it's going to roll back the entire load after that one warning, it should terminate there. AFAIK, a warning is no reason for PostgreSQL to roll back anything. That's the difference between a warning and an error. HTH, Markus -- Markus Schaber | Logical TrackingTracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in Europe! www.ffii.org www.nosoftwarepatents.org signature.asc Description: OpenPGP digital signature
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Ühel kenal päeval, P, 2006-09-24 kell 10:20, kirjutas Peter Eisentraut: Alvaro Herrera wrote: On the other hand, I don't understand why DocBook would be Latin-1 only. What would be the point of that limitation? Some googling seems to reveal that people indeed uses other charsets, UTF-8 in particular (but also Big5, Latin-2, etc), so apparently this isn't set in stone. (I admit that they mainly talk about XML Docbook though). DocBook SGML is Latin 1; DocBook XML, like all XML, is UCS-4. Are you sure it's UCS-4 ? I've always thought that XML is what is given in xml tag, and utf-8 if no charset is given. -- Hannu Krosing Database Architect Skype Technologies OÜ Akadeemia tee 21 F, Tallinn, 12618, Estonia Skype me: callto:hkrosing Get Skype for free: http://www.skype.com ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Hi, Hannu, Hannu Krosing wrote: Are you sure it's UCS-4 ? I've always thought that XML is what is given in xml tag, and utf-8 if no charset is given. You have to distinguish between the supported charset, and the document encoding. HTH, Markus -- Markus Schaber | Logical TrackingTracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in Europe! www.ffii.org www.nosoftwarepatents.org signature.asc Description: OpenPGP digital signature
[HACKERS] AllocFile debug code
http://archives.postgresql.org/pgsql-committers/2006-08/msg00410.php Should this be removed again now? The actual fix should be http://archives.postgresql.org/pgsql-committers/2006-08/msg00504.php, and per http://archives.postgresql.org/pgsql-hackers/2006-08/msg01920.php it seems to have solved the problem? (It does log the error for pgstat.stat on every single server startup, which is why I noticed it) //Magnus ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[HACKERS] Logfile created when not needed?
Digging into several win32 related issues right now, so I don't have the time to investigate ATM, but I figured I should get it out here: If I configure log_destination='eventlog', and then redirect_stderr='on', PostgreSQL will attempt to create a logfile in pg_log anyway. This file remains empty (at least through my test), but it is created, and if it fails to be created, the postmaster won't start at all. I may be missing something and there is a point to this, but if it's never used it should probably not be created in the first place, should it? (I would assume the same thing happens if you set log_destination='syslog', but haven't tested that) //Magnus ---(end of broadcast)--- TIP 6: explain analyze is your friend
[HACKERS] pg_regress starting postmaster
subject says it all. pg_regress starts postmaster (pg_regress.c, line 1515). Shouldn't this be postgres these days? (Yes, I'm aware that I wrote that code ;-) But this just occurred to me..) //Magnus ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] pg_regress starting postmaster
subject says it all. pg_regress starts postmaster (pg_regress.c, line 1515). Shouldn't this be postgres these days? (Yes, I'm aware that I wrote that code ;-) But this just occurred to me..) Actually, a second thought given that I was just bitten by the run-tests-as-admin-doesn't-work - should we use pg_ctl to start it? //Magnus ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] pg_regress starting postmaster
Magnus Hagander [EMAIL PROTECTED] writes: subject says it all. pg_regress starts postmaster (pg_regress.c, line 1515). Shouldn't this be postgres these days? No. We're a very long way away from considering removing the postmaster symlink, so it doesn't matter. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] pg_regress starting postmaster
Magnus Hagander [EMAIL PROTECTED] writes: Actually, a second thought given that I was just bitten by the run-tests-as-admin-doesn't-work - should we use pg_ctl to start it? No, not unless you'd like to break pg_regress's ability to kill the postmaster --- we need the postmaster to be the direct child process. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] PostgreSQL 8.2beta1 w/ VALUES
Luke Lonergan [EMAIL PROTECTED] writes: If it's going to roll back the entire load after that one warning, it should terminate there. This was a warning, not an error. regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Buildfarm alarms
Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: It could certainly be done. In general, I have generally taken the view that owners have the responsibility for monitoring their own machines. Sure, but providing them tools to do that seems within buildfarm's purview. For some types of failure, the buildfarm script could make a local notification without bothering the server --- but a timeout on the server side would cover a wider variety of failures, including this machine is dead and ought to be removed from the farm. Nothing gets removed. If a machine does not report on a branch for 30 days it drops off the dashboard, but apart from that it is a retained historic aretfact. This buildup in history has been gradually slowing down the dashboard, in fact, but Ian Barwick tells me that he has rewritten my lousy SQL to make it fast again, so we'll soon get that working better. Anyway, I think we can do something fairly simply for these alarms. We'll just have a special stanza in the config file, and a cron job that checks, say, once a day, to see if we have exceeded the alarm period on any machine/branch combination. cheers andrew ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] pg_regress starting postmaster
subject says it all. pg_regress starts postmaster (pg_regress.c, line 1515). Shouldn't this be postgres these days? No. We're a very long way away from considering removing the postmaster symlink, so it doesn't matter. Well, per previous discussion, we're removing postmaster.exe from the win32 installer, because it bloats the distribution wihtout any gain (remember - windows doesn't have symlinks, so we need a complete copy of a file that's 4Mb or so). So it would matter there. Actually, a second thought given that I was just bitten by the run-tests-as-admin-doesn't-work - should we use pg_ctl to start it? No, not unless you'd like to break pg_regress's ability to kill the postmaster --- we need the postmaster to be the direct child process. D'oh, forgot about that. Nevermind about that part then. //Magnus ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] AllocFile debug code
Magnus Hagander [EMAIL PROTECTED] writes: http://archives.postgresql.org/pgsql-committers/2006-08/msg00410.php Should this be removed again now? I was intending to remove it sometime before release, but seeing that a number of the Windows buildfarm members have been out of commission for the last several weeks, I'm unsure whether we have enough test runs yet to be sure the problem is fixed ... regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] pgsql: We're going to have to spell dotless i
On Sun, Sep 24, 2006 at 10:20:22AM +0200, Peter Eisentraut wrote: Alvaro Herrera wrote: On the other hand, I don't understand why DocBook would be Latin-1 only. What would be the point of that limitation? Some googling seems to reveal that people indeed uses other charsets, UTF-8 in particular (but also Big5, Latin-2, etc), so apparently this isn't set in stone. (I admit that they mainly talk about XML Docbook though). DocBook SGML is Latin 1; DocBook XML, like all XML, is UCS-4. This sheds a new light on the XML vs. SGML thing you said before. While it's not necessarily compelling enough to force a switch, it is a substantive difference that we can actually see. Cheers, D -- David Fetter [EMAIL PROTECTED] http://fetter.org/ phone: +1 415 235 3778AIM: dfetter666 Skype: davidfetter Remember to vote! ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] AllocFile debug code
http://archives.postgresql.org/pgsql-committers/2006-08/msg00410.php Should this be removed again now? I was intending to remove it sometime before release, but seeing that a number of the Windows buildfarm members have been out of commission for the last several weeks, I'm unsure whether we have enough test runs yet to be sure the problem is fixed ... Yeah, seems reasonable to keep around for a bit longer. It should probably be added to the release checklist so we remember to get it done before we roll RC at least? //Magnus ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] pg_regress starting postmaster
Magnus Hagander [EMAIL PROTECTED] writes: No. We're a very long way away from considering removing the postmaster symlink, so it doesn't matter. Well, per previous discussion, we're removing postmaster.exe from the win32 installer, because it bloats the distribution wihtout any gain (remember - windows doesn't have symlinks, so we need a complete copy of a file that's 4Mb or so). So it would matter there. Well, you could copy postgres.exe to postmaster.exe during install, so I don't think you ever did need to bloat the distribution, only the install footprint. The question here is whether you're ready to break existing custom scripts for starting the postmaster. Maybe there are none such in the wild on Windows, but I'd be hesitant to assume that. regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] pg_regress starting postmaster
No. We're a very long way away from considering removing the postmaster symlink, so it doesn't matter. Well, per previous discussion, we're removing postmaster.exe from the win32 installer, because it bloats the distribution wihtout any gain (remember - windows doesn't have symlinks, so we need a complete copy of a file that's 4Mb or so). So it would matter there. Well, you could copy postgres.exe to postmaster.exe during install, so I don't think you ever did need to bloat the distribution, only the install footprint. Except you're not supposed to do that, because the MSI auto-healing and things like that won't work... The question here is whether you're ready to break existing custom scripts for starting the postmaster. Maybe there are none such in the wild on Windows, but I'd be hesitant to assume that. We're guessing there aren't - if there are, those are scripts calling the SCM which in turns starts postgresql. So we're doing it now - if it turns up in beta that people were actually using it from elsewhere, we'll jus thave to put it back. //Magnus ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] [PATCHES] Bad bug in fopen() wrapper code
Magnus Hagander [EMAIL PROTECTED] writes: Attached patch sets the O_CREAT option when appending to files. That looks correct, but I went looking to see if there were any other mistakes of the same ilk, and I'm wondering what the sense is in openFlagsToCreateFileFlags ... seems like it's ignoring O_EXCL in some combinations and not others. Is that right? regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] [PATCHES] pg_ctl error msg on Windows 2000
Magnus Hagander [EMAIL PROTECTED] writes: On version of Windows prior to XP, pg_ctl will *always* log a warning about not finding Job API functions. This is probably unnecessary, since they are never present there. The check was originally intended to give a warning if something was wrong on a system where it was *expected*. Attached patch checks the OS version before emitting the error message. Applied. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] pg_regress starting postmaster
Magnus Hagander [EMAIL PROTECTED] writes: The question here is whether you're ready to break existing custom scripts for starting the postmaster. Maybe there are none such in the wild on Windows, but I'd be hesitant to assume that. We're guessing there aren't - if there are, those are scripts calling the SCM which in turns starts postgresql. So we're doing it now - if it turns up in beta that people were actually using it from elsewhere, we'll jus thave to put it back. OK. Well, there's certainly no harm in making pg_regress execute postgres instead of postmaster, so I'll change that. regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] [PATCHES] Bad bug in fopen() wrapper code
Attached patch sets the O_CREAT option when appending to files. That looks correct, but I went looking to see if there were any other mistakes of the same ilk, and I'm wondering what the sense is in openFlagsToCreateFileFlags ... seems like it's ignoring O_EXCL in some combinations and not others. Is that right? That is part of the original open() code that Claudio did back for 8.0, so it has definitly been working since then. I haven't really read into the code, though... But a qiuck look doesn't show me any place wher eit does ignore O_EXCL - which combination would that be? //Magnus ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] pg_regress starting postmaster
The question here is whether you're ready to break existing custom scripts for starting the postmaster. Maybe there are none such in the wild on Windows, but I'd be hesitant to assume that. We're guessing there aren't - if there are, those are scripts calling the SCM which in turns starts postgresql. So we're doing it now - if it turns up in beta that people were actually using it from elsewhere, we'll jus thave to put it back. OK. Well, there's certainly no harm in making pg_regress execute postgres instead of postmaster, so I'll change that. Thanks. //Magnus ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] [PATCHES] Updates to pg_regress.c
Magnus Hagander [EMAIL PROTECTED] writes: Found a couple of XXX is there a way to do this on Windows in pg_regress.c that I had missed. The answer to the question is yes, attached is a patch that does it. Applied, along with change to make it start the temp postmaster as postgres not postmaster. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] [PATCHES] Bad bug in fopen() wrapper code
Magnus Hagander [EMAIL PROTECTED] writes: That is part of the original open() code that Claudio did back for 8.0, so it has definitly been working since then. Hm, maybe best not to touch it, but still... I haven't really read into the code, though... But a qiuck look doesn't show me any place wher eit does ignore O_EXCL - which combination would that be? What's bugging me is that 0 and O_EXCL give the same answer, and O_TRUNC and O_TRUNC | O_EXCL give the same answer, but O_CREAT and O_CREAT | O_EXCL give different answers, as do O_CREAT | O_TRUNC and O_CREAT | O_TRUNC | O_EXCL. I'm also pretty suspicious of both O_CREAT | O_EXCL and O_CREAT | O_TRUNC | O_EXCL giving the same answer. However, I have no idea what the semantics are of the symbols the function is mapping into, so maybe it's OK. regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] [PATCHES] Bad bug in fopen() wrapper code
Magnus Hagander [EMAIL PROTECTED] writes: This is pretty bad and pretty urgent - with this, systems installed by the MSI installer simply *do not start*, because they are by default configured to write logs to a file... Attached patch sets the O_CREAT option when appending to files. Applied, but I'm still wondering about openFlagsToCreateFileFlags() ... regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] Logfile created when not needed?
Magnus Hagander [EMAIL PROTECTED] writes: If I configure log_destination='eventlog', and then redirect_stderr='on', PostgreSQL will attempt to create a logfile in pg_log anyway. So don't do that --- redirect_stderr is only sensible to turn on if you mean to use logging to stderr. The reason we don't attempt to enforce this is that log_destination is legal to change after startup, whereas we can't change redirect_stderr on-the-fly (because existing backends wouldn't have their stderr tied to the right place). I'm not sure how sensible it really is to switch dynamically between logging to stderr and logging someplace else, but as long as the code can support that, why not allow it ... regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Logfile created when not needed?
If I configure log_destination='eventlog', and then redirect_stderr='on', PostgreSQL will attempt to create a logfile in pg_log anyway. So don't do that --- redirect_stderr is only sensible to turn on if you mean to use logging to stderr. I don't. Normally. But I had it turned on, then changed log_destination and forgot.. The reason we don't attempt to enforce this is that log_destination is legal to change after startup, whereas we can't change redirect_stderr on-the-fly (because existing backends wouldn't have their stderr tied to the right place). Ok. Fair 'nuf. //Magnus ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[HACKERS] Windows build farm failures
Snake and Bandicoot are still hanging in ECPG-Check at the moment. Killing the dt_test.exe program that the regression tests seem to be running frees it all up to properly report the failure. I don't have time to investigate further at the minute, but for anyone that does, Bandicoot's last run was completed only by killing dt_test.exe, whereas Snakes was a little more random :-) Regards Dave. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [PATCHES] Include file in regress.c
That definitely looks weird to me. Unfortunatly, it's way above me wrt CVS knowledge. I'm just going to have to live with it and remember to delete that part from my diffs... The weird thing is that it's not happening for other people. Have you tried blowing away the whole tree and doing a fresh checkout? What CVS version are you using? Haven't tried that, but I will eventually (need to clean up some of the stuff I have in the tree first). I'm on: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build 2064 (client/server) CVSNT version (Aug 19 2005) Copyright (c) 1999-2005 Tony Hoyle and others //Magnus ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Ühel kenal päeval, P, 2006-09-24 kell 14:56, kirjutas Markus Schaber: Hi, Hannu, Hannu Krosing wrote: Are you sure it's UCS-4 ? I've always thought that XML is what is given in xml tag, and utf-8 if no charset is given. You have to distinguish between the supported charset, and the document encoding. UCS-4 and UTF-8 are both encodings for UNICODE see: http://en.wikipedia.org/wiki/UTF-32 HTH, Markus -- Hannu Krosing Database Architect Skype Technologies OÜ Akadeemia tee 21 F, Tallinn, 12618, Estonia Skype me: callto:hkrosing Get Skype for free: http://www.skype.com ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Hannu Krosing wrote: Ühel kenal päeval, P, 2006-09-24 kell 14:56, kirjutas Markus Schaber: Hi, Hannu, Hannu Krosing wrote: Are you sure it's UCS-4 ? I've always thought that XML is what is given in xml tag, and utf-8 if no charset is given. You have to distinguish between the supported charset, and the document encoding. UCS-4 and UTF-8 are both encodings for UNICODE see: http://en.wikipedia.org/wiki/UTF-32 If we want to quote references, we should quote the XML standard. For example, see here to see the exact charset supported by XML: http://www.w3.org/TR/2006/REC-xml11-20060816/#charsets. A little lower down it defines the encodings allowed too. cheers andrew ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Andrew Dunstan wrote: If we want to quote references, we should quote the XML standard. For example, see here to see the exact charset supported by XML: http://www.w3.org/TR/2006/REC-xml11-20060816/#charsets. The actual cause of the processing problems we have been seeing are the character set definitions in the SGML declarations of the respective document types. For DocBook SGML 4.2: CHARSET BASESET ISO 646:1983//CHARSET International Reference Version (IRV)//ESC 2/5 4/0 DESCSET 0 9 UNUSED 9 2 9 11 2 UNUSED 13 113 14 18 UNUSED 32 9532 127 1 UNUSED BASESET ISO Registration Number 100//CHARSET ECMA-94 Right Part of Latin Alphabet Nr. 1//ESC 2/13 4/1 DESCSET 128 32 UNUSED 160 96 32 For XML: CHARSET BASESET ISO Registration Number 177//CHARSET ISO/IEC 10646-1:1993 UCS-4 with implementation level 3//ESC 2/5 2/15 4/6 DESCSET 09 UNUSED 92 9 112 UNUSED 131 13 14 18 UNUSED 32 95 32 1271 UNUSED 128 32 UNUSED 16055136 160 55296 2048 UNUSED -- surrogates -- 57344 8190 57344 655342 UNUSED -- FFFE and -- 65536 1048576 65536 -- 16 planes outside BMP -- -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PATCHES] [HACKERS] large object regression tests
On Thu, 21 Sep 2006, Tom Lane wrote: Jeremy Drake [EMAIL PROTECTED] writes: I put together a patch which adds a regression test for large objects, hopefully attached to this message. I would like some critique of it, to see if I have gone about it the right way. Also I would be happy to hear any additional tests which should be added to it. I'd prefer it if we could arrange not to need any absolute paths embedded into the test, because maintaining tests that require such is a real PITA --- instead of just committing the actual test output, one has to reverse-convert it to a .source file. I just copied how the test for COPY worked, since I perceived a similarity in what I needed to do (use external files to load data). I suggest that instead of testing the server-side lo_import/lo_export functions, perhaps you could test the psql equivalents and write and read a file in psql's working directory. I did not see any precedent for that when I was looking around in the existing tests for an example of how to do things. I am not even sure where the cwd of psql is, so I can put an input file there. Could you provide an example of how this might look, by telling me where to put a file in the src/test/regress tree and the path to give to \lo_import? Besides which, shouldn't both the server-side and psql versions be tested? When I was looking at the copy tests, it looked like the server-side ones were tested, and then the psql ones were tested by exporting and then importing data which was originally loaded from the server-side method. Am I correctly interpreting the precedent, or are you suggesting that the precedent be changed? I was trying to stay as close to the copy tests as possible since the functionality is so similar (transferring data to/from files in the filesystem, either via server-side functions which require absolute paths or via psql \ commands (which I forgot about for the lo funcs)). I think we could do without the Moby Dick extract too ... I am open to suggestions. I saw one suggestion that I use an image of an elephant, but I suspect that was tongue-in-cheek. I am not very fond of the idea of generating repetitious data, as I think it would be more difficult to determine whether or not the loseek/tell functions put me in the right place in the middle of the file. Perhaps if there was a way to generate deterministic pseudo-random data, that would work (has to be deterministic so the diffs of the output come out right). Anyone have a good example of seeding a random number generator and generating a bunch of bytea which is deterministic cross-platform? regards, tom lane In the mean time, I will alter the test to also test the psql backslash commands based on how the copy equivalents are tested, since I had forgotten them and they need to be tested also. -- Any sufficiently advanced technology is indistinguishable from a rigged demo. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] AllocFile debug code
Added to open items list. --- Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] writes: http://archives.postgresql.org/pgsql-committers/2006-08/msg00410.php Should this be removed again now? I was intending to remove it sometime before release, but seeing that a number of the Windows buildfarm members have been out of commission for the last several weeks, I'm unsure whether we have enough test runs yet to be sure the problem is fixed ... regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Ühel kenal päeval, E, 2006-09-25 kell 00:23, kirjutas Peter Eisentraut: Andrew Dunstan wrote: If we want to quote references, we should quote the XML standard. For example, see here to see the exact charset supported by XML: http://www.w3.org/TR/2006/REC-xml11-20060816/#charsets. The actual cause of the processing problems we have been seeing are the character set definitions in the SGML declarations of the respective document types. I see charsets, but where are encodings defined ? I don't think that any of our SGML documentation is actually in UCS-4 encoding. -- Hannu Krosing Database Architect Skype Technologies OÜ Akadeemia tee 21 F, Tallinn, 12618, Estonia Skype me: callto:hkrosing Get Skype for free: http://www.skype.com ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Hannu Krosing [EMAIL PROTECTED] writes: I don't think that any of our SGML documentation is actually in UCS-4 encoding. The source files use nothing beyond plain ASCII (and should remain that way, IMHO) so there isn't any need to inquire very far into exactly what the toolchain thinks the document encoding is. The issue at hand here is what the *output* character set is, which is to say the document character set if I have the jargon right. That is the space over which we are permitted to use -entities. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[HACKERS] TODO: Fix CREATE CAST on DOMAIN Part II
Continuing the discussion about domain cast problem... http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php Tom, I have done some playing and thinking about the problem... You are absolutely right about the points you mentioned on http://archives.postgresql.org/pgsql-hackers/2006-09/msg01690.php I am planning to investigate the behavior of other DBMSs regarding domain casting (after this cast is off my wrist this week, so I can type normally again) Perhaps I gain a new perspective to continue preparing a proposal... -- Regards, Gevik Babakhani ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] pgsql: We're going to have to spell dotless i
Tom Lane wrote: Hannu Krosing [EMAIL PROTECTED] writes: I don't think that any of our SGML documentation is actually in UCS-4 encoding. The source files use nothing beyond plain ASCII (and should remain that way, IMHO) so there isn't any need to inquire very far into exactly what the toolchain thinks the document encoding is. The issue at hand here is what the *output* character set is, which is to say the document character set if I have the jargon right. That is the space over which we are permitted to use -entities. Just for reference, if we could support UTF8, I was hoping to add non-Latin names as alternates to the ASCII versions, so we could have Japanese and Russian-lettered names in the release notes. I thought it would be a nice touch. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[HACKERS] pls disregard, testing majordomo settings
I just messed with a bunch of my majordomo settings and I wanted to make sure things are working the way I thought. Please disregard. Sorry to bother everyone -- I'll defend to the death your right to say that, but I never said I'd listen to it! -- Tom Galloway with apologies to Voltaire ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] Questions about guc units
Hi hackers, I have some questions about guc units, new feature in 8.2. #shared_buffers = 32000kB # min 128kB or max_connections*16kB #temp_buffers = 8000kB # min 800kB #effective_cache_size = 8000kB Are there any reasons to continue to use 1000-unit numbers? Megabyte-unit (32MB and 8MB) seems to be more friendly for users. It increases some amount of values (4000 vs. 4096), but there is little in it. #max_fsm_pages = 160# min max_fsm_relations*16, 6 bytes each #wal_buffers = 8# min 4, 8kB each They don't have units now, but should they have GUC_UNIT_BLOCKS and GUC_UNIT_XLOG_BLCKSZ unit? I feel inconsistency in them. Regards, --- ITAGAKI Takahiro NTT Open Source Software Center ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [PATCHES] Bad bug in fopen() wrapper code
Hello guys, it's been a while, but... What's bugging me is that 0 and O_EXCL give the same answer, and O_TRUNC and O_TRUNC | O_EXCL give the same answer, This is ok, as (iirc) O_EXCL only has effect in the presence of O_CREAT. (a comment to this effect would help here, as well as perhaps links to the CreateFile and open specs) but O_CREAT and O_CREAT | O_EXCL give different answers, as do O_CREAT | O_TRUNC and O_CREAT | O_TRUNC | O_EXCL. See above. I'm also pretty suspicious of both O_CREAT | O_EXCL and O_CREAT | O_TRUNC | O_EXCL giving the same answer. O_CREAT | O_EXCL is effectively create, but fail if the file exists, which is the behaviour specified by CREATE_NEW. Adding O_TRUNC to this combination, which can only apply to a successfully opened existent file, can have no impact afaics. Cheers, Claudio ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [PATCHES] [HACKERS] large object regression tests
On Sun, 24 Sep 2006, Jeremy Drake wrote: On Thu, 21 Sep 2006, Tom Lane wrote: I suggest that instead of testing the server-side lo_import/lo_export functions, perhaps you could test the psql equivalents and write and read a file in psql's working directory. I did not see any precedent for that when I was looking around in the existing tests for an example of how to do things. snip When I was looking at the copy tests, it looked like the server-side ones were tested, and then the psql ones were tested by exporting and then importing data which was originally loaded from the server-side method. I just went back and looked at the tests again. The only time the psql \copy command was used was in the (quite recent IIRC) copyselect test, and then only via stdout (never referring to psql working directory, or to files at all). Did I misunderstand, and you are proposing a completely new way of doing things in the regression tests? I am not particularly fond of the sed substitution stuff myself, but it seems to be the only currently supported/used method in the regression tests... I do think that making the large object test and the copy test consistent would make a lot of sense, since as I said before, the functionality of file access is so similar... -- We demand rigidly defined areas of doubt and uncertainty! -- Vroomfondel ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] pgsql: We're going to have to spell dotless i
On Sun, Sep 24, 2006 at 07:38:20PM -0400, Tom Lane wrote: Hannu Krosing [EMAIL PROTECTED] writes: I don't think that any of our SGML documentation is actually in UCS-4 encoding. The source files use nothing beyond plain ASCII (and should remain that way, IMHO) so there isn't any need to inquire very far into exactly what the toolchain thinks the document encoding is. The issue at hand here is what the *output* character set is, which is to say the document character set if I have the jargon right. That is the space over which we are permitted to use -entities. What you're talking about is generally referred to as the character repertoire, the abstract set of characters a document is considered to be composed of. For example: HTML4 (and XML IIRC) explicitly defines the character repertoire to be Unicode, even though the character encoding may only point to a subset of the total. Any others can be generated via the xxx; escape syntax. I'm surprised about the difference in installations. I didn't use your -c option because that directory does not exist on my computer, but maybe that's all the difference... http://www.unicode.org/unicode/reports/tr17/ Have a nice day, -- Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/ From each according to his ability. To each according to his ability to litigate. signature.asc Description: Digital signature
