threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "> > Was the following bug already fixed ?\n> \n> Dunno. I've changed the WAL ReadRecord code so that it fails soft (no\n> Asserts or elog(STOP)s) for all failure cases, so the particular crash\n> mode exhibited here should be gone. But I'm not sure why the code\n> appears to be trying to op... |
[
{
"msg_contents": "> > I see that seek+write was changed to write-s in XLogFileInit\n> > (that was induced by subj, right?), but what about problem\n> > itself?\n> \n> > BTW, were performance tests run after seek+write --> write-s\n> > change?\n> \n> That change was for safety, not for performance. It might be... |
[
{
"msg_contents": "I am currently looking at a frozen system: a backend crashed during XLOG\nwrite (which I was deliberately provoking, via running it out of disk\nspace), and now the postmaster is unable to recover because it's waiting\naround for a checkpoint process that it had launched milliseconds before\n... |
[
{
"msg_contents": "Greetings,\n\nI have a real simple table with a timestamp field. The timestamp field has \nan index on it. But, the index does not seem to be taken into account for \nselects that return rows:\n\npglog=# explain select time_stamp from history_entries where time_stamp < \n'03-01-2000';\nNOTI... |
[
{
"msg_contents": "> > It seems that you want guarantee more than me, Tom -:)\n> \n> No, but I want a system that's not brittle. You seem to be content to\n> design a system that is reliable as long as the WAL log is OK \n> but loses the entire database unrecoverably as soon as one bit goes bad\n> in the log.\n... |
[
{
"msg_contents": "> Eventually the checkpoint process will time out the spinlock and abort\n> (but please note that this is true only because I insisted --- Vadim\n> wanted to have infinite timeouts on the WAL spinlocks. I think this is\n> good evidence that that's a bad idea).\n\nI disagree - this is evidence... |
[
{
"msg_contents": "> Other than what we've discussed, do you have any \n> comments/objections to my proposed patch?\n> I've been holding off committing it so that you have\n> time to review it...\n\nSorry - I'm heading to meet Marc, Thomas & Geoff right now,\nwill try to comment asap.\n\nVadim\n",
"msg_date... |
[
{
"msg_contents": "To implement the idea of performing a checkpoint after every so many\nXLOG megabytes (as well as after every so many seconds), I need to pick\nan additional signal number for the postmaster to accept. Seems like\nthe most appropriate choice for this is SIGUSR1, which isn't currently\nbeing u... |
[
{
"msg_contents": "Greetings,\n\nSorry about all the posts lately, but things seems to be running *really* \nslow on my database. I have two tables, both are identical and one is used \nto hold entries older than a certain date, i.e. the history table. I use \nthis query to move the old records from one to th... |
[
{
"msg_contents": "Greetings,\n\nSorry about all the posts lately, but things seems to be running *really* \nslow on my database. I have two tables, both are identical and one is used \nto hold entries older than a certain date, i.e. the history table. I use \nthis query to move the old records from one to th... |
[
{
"msg_contents": "hi,\nI an using postgresql-7.1beta4 and am trying to use the large text fields. \nI have heard of TOAST. There is little documentation. \n I found one section about creating a data type,\nthen creating two functions to convert the data types.\nIs this how TOAST is implemented?\nAm I on the r... |
[
{
"msg_contents": "In case anyone cares, there is a bug in pg_dump in 7.0.3 when using the bit\nfields.\n\neg: (This is a dump)\n\nINSERT INTO \"menu_plans\" VALUES (7,'B''100000000''');\nINSERT INTO \"menu_plans\" VALUES (6,'B''100000000''');\nINSERT INTO \"menu_plans\" VALUES (8,'B''100000000''');\n\nI think ... |
[
{
"msg_contents": "\n> > Even with true fdatasync it's not obviously good for performance - it takes\n> > too long time to write 16Mb files and fills OS buffer cache with trash-:(\n> \n> True. But at least the write is (hopefully) being done at a\n> non-performance-critical time.\n\nSo you have non critical ti... |
[
{
"msg_contents": "Hi,\n\nI'm wondering how safe it is to pass an uninitialized conn to\nPQfinish....\n\nI have set a SIGALRM handler that terminates my daemon and closes\nconnection\nto Postgres if time-out happens. However, Im setting the alarm few times\nbefore the connection to Postgres was established... w... |
[
{
"msg_contents": "> > Even with true fdatasync it's not obviously good for performance - it takes\n> > too long time to write 16Mb files and fills OS buffer cache \n> with trash-:(\n> >> \n> >> True. But at least the write is (hopefully) being done at a\n> >> non-performance-critical time.\n> \n> > So you hav... |
[
{
"msg_contents": "\n> > A short test shows, that opening the file O_SYNC, and thus avoiding fsync()\n> > would cut the effective time needed to sync write the xlog more than in half.\n> > Of course we would need to buffer >= 1 xlog page before write (or commit)\n> > to gain the full advantage.\n> \n> > prewrit... |
[
{
"msg_contents": "OK, I have finished the first version of my performance monitor. You\ncan get the TCL code at:\n\n\tftp://candle.pha.pa.us/pub/postgresql/pgtop.tcl\n\nOnce people like it, I will add it to CVS /contrib. It probably will\nonly work only *BSD and Linux right now. It tries to find the USER an... |
[
{
"msg_contents": "\n> > > Of course we would need to buffer >= 1 xlog page before write (or commit)\n> > > to gain the full advantage.\n> > \n> > > prewrite 0 + write and fsync:\t\t60.4 sec\n> > > sparse file + write with O_SYNC:\t\t37.5 sec\n> > > no prewrite + write with O_SYNC:\t\t36.8 sec\n> > > prewrite 0... |
[
{
"msg_contents": "\n> >> This seems odd. As near as I can tell, O_SYNC is simply a command to do\n> >> fsync implicitly during each write call. It cannot save any I/O unless\n> >> I'm missing something significant. Where is the performance difference\n> >> coming from?\n> \n> > Yes, odd, but sure very repro... |
[
{
"msg_contents": "Hi pgsql-hackers,\n\nI'm currently porting 7.0.3 to the HP MPE/iX OS to join my other ports of\nApache, BIND, sendmail, Perl, and others. I'm at the point where I'm trying to\nrun the \"make runcheck\" regression tests, and I've just run into a problem\nwhere I need to seek the advice of psq... |
[
{
"msg_contents": "> > Even with true fdatasync it's not obviously good for \n> > performance - it takes too long time to write 16Mb files\n> > and fills OS buffer cache with trash-:(\n> \n> True. But at least the write is (hopefully) being done at a\n> non-performance-critical time.\n\nThere is no such hope: ... |
[
{
"msg_contents": "> The reason I'm inclined to question this is that what we want \n> is not an fsync per write but an fsync per transaction, and we can't \n> easily buffer all of a transaction's XLOG writes...\n\nWAL keeps records in WAL buffers (wal-buffers parameter may be used to\nincrease # of buffers), s... |
[
{
"msg_contents": "> > But needed if we want to get rid of vacuum and have savepoints.\n> \n> Hmm. How do you implement savepoints ? When there is rollback \n> to savepoint do you use xlog to undo all changes which the particular \n> transaction has done ? Hmmm it seems nice ... these resords are locked by \n> ... |
[
{
"msg_contents": "Jeff Lu writes:\n\n> $ make intrasend\n> gcc -o /c/inetpub/wwwroot/cgi-bin/intrasend.exe intrasend.c\n> intrautils.c -I/usr/\n> local/pgsql/include -L/usr/local/pgsql/lib\n\n-lpq\n\n> intrautils.c:7: warning: initialization makes integer from pointer without a\n> cas\n> t\n> /c/TEMP/ccXES02E.... |
[
{
"msg_contents": "Now you're talking about i18n, maybe someone could think about input and\noutput of dates in local language.\n\nAs fas as I can tell, PostgreSQL will only use English for dates, eg January,\nFebruary and weekdays, Monday, Tuesday etc. Not the local name.\n\n-- \nKaare Rasmussen --L... |
[
{
"msg_contents": "> I tried this on HPUX 10.20, which has not only O_SYNC but also O_DSYNC\n> (defined to do the equivalent of fdatasync()), and got truly \n> fascinating results. Apparently, on this platform these flags change\n> the kernel's buffering behavior! Observe:\n\nSolaris 2.6 fascinates even more!!... |
[
{
"msg_contents": "> $ gcc -Wall -O -DINIT_WRITE tfsync.c\n> $ time a.out\n> \n> real 1m15.11s\n> user 0m0.04s\n> sys 0m32.76s\n> \n> Note the large amount of system time here, and the fact that the extra\n> time in INIT_WRITE is all system time. I have previously \n> observed that fsync() on HPUX 10... |
[
{
"msg_contents": "Assume a configuration problem that causes standalone backends to fail\nwithout doing anything. (I happened across this by tweaking global.bki\nin such a way that the superuser name entered into pg_shadow was\ndifferent from what getpwname returns. I don't have a real-world\nexample, but I'... |
[
{
"msg_contents": "\"Mikheev, Vadim\" <vmikheev@SECTORBASE.COM> writes:\n> Tom, could you run this test for different block sizes?\n> Up to 32*8k?\n>> \n>> You mean changing the amount written per write(), while holding the\n>> total file size constant, right?\n\n> Yes. Currently XLogWrite writes 8k blocks one ... |
[
{
"msg_contents": "> $ gcc -Wall -O -DINIT_WRITE -DUSE_DSYNC -DBLOCKS=1 tfsync.c\n ^^^^^^^^^^^\nYou should use -DUSE_OSYNC to test O_SYNC.\nSo you've tested N * write() + fsync(), exactly what I've asked -:)\n\n> So I also see that there is no benefit to writing more than \n> one bl... |
[
{
"msg_contents": "> Starting to look like we should just use ODSYNC where available, and\n> forget about dumping more per write ...\n\nI'll run these tests on RedHat 7.0 tomorrow.\n\nVadim\n",
"msg_date": "Fri, 9 Mar 2001 18:45:36 -0800 ",
"msg_from": "\"Mikheev, Vadim\" <vmikheev@SECTORBASE.COM>",
... |
[
{
"msg_contents": "> > So seems we can use O_DSYNC without losing log write performance\n> > comparing with write() + fsync. Though, we didn't tested write() +\n> > fdatasync() yet...\n> \n> Good point, we should check fdatasync() too --- although I have no\n> machines where it's different from fsync().\n\nI've... |
[
{
"msg_contents": "Is this page \n\n http://members.fortunecity.com/nymia/postgres/dox/backend/html/\n\ncommon knowledge? It appears to be an automatically-generated\ncross-reference documentation web site. My impression is that\nappropriately-marked comments in the code get extracted to the \nweb pages, too... |
[
{
"msg_contents": "At the end of backend/utils/adt/datetime.c, there is some fairly ugly\ncode that is conditionally compiled on\n\n#if defined(linux) && defined(__powerpc__)\n\nDo we still need this? The standard versions of TIMESTAMP_IS_CURRENT\nand TIMESTAMP_IS_EPOCH appear to work just fine on my Powerbook... |
[
{
"msg_contents": "I have applied the following patch to make SIGTERM backend exit clearer\nin the the server logs. \"The system\" is not really shutting down, but\n\"the backend\" is shutting down.\n\nShould we be showing the PID's in the server logs more. Do we need to\nenable that somewhere? Seems they ar... |
[
{
"msg_contents": "I have completed version 0.1 of pgtop, a PostgreSQL session monitor. \nScreenshot attached.\n\nI show the currently running query by using gdb to attach to a running\nbackend. The backend must have debug symbols and the 'postgres' binary\nmust be in the current patch. I check for both of th... |
[
{
"msg_contents": "Hello,\n\nWe have built a database application build around PostgreSQL v7.03. \nAnd we're very happy with PostgreSQL functionality & performance.\n\nIn a live situation 50-100 clients are inserting and updating database\nrecords. It is very important that we have all the data available on\n... |
[
{
"msg_contents": "I am trying to debug my socket-level interface to the backend, which\nimplements the 6.4 protocol. It works for general queries, but I have\na problem with large objects.\n\nlo_create and lo_unlink seem to work OK; I get an oid which looks ok\nand there is a corresponding xinv??? file in the ... |
[
{
"msg_contents": "doxygen is a great tool to make code documentation...\n\nIt is particulary easy for developpers to add /** **/ comments instead of\n/* */ comments that will be extracted by doxygen to make documentation on\nfunctions, structures,...\n\nthen you run doxygen from cron and you get automatic API... |
[
{
"msg_contents": "I have renamed pgtop.tcl to pgmonitor. I think the new name is clearer.\n\n\tftp://candle.pha.pa.us/pub/postgresql/pgmonitor\n\n-- \n Bruce Momjian | http://candle.pha.pa.us\n pgman@candle.pha.pa.us | (610) 853-3000\n + If your life is a hard drive,... |
[
{
"msg_contents": "\n\tWhile testing some existing database applications on 7.1beta4 on\nmy Sparc 20 running Debian GNU/Linux 2.2, I got the following error on\nattempting to do a vacuum of a table:\n\nNOTICE: FlushRelationBuffers(jobs, 1399): block 953 is referenced (private 0, global 1)\nERROR! Can't vacuum ... |
[
{
"msg_contents": "At 06:11 06/03/01 -0500, Vince Vielhaber wrote:\n\n>This just came to the webmaster mailbox:\n\nSorry for the delay, busy week...\n\n\n>-------\n>Most of the top banner links on http://jdbc.postgresql.org (like\n>Documentation, Tutorials, Resources, Development) throw up 404s if\n>followed. T... |
[
{
"msg_contents": "\n> Ok, I've made changes in xlog.c and run tests: 50 clients inserted\n> (int4, text[1-256]) into 50 tables,\n> -B 16384, -wal_buffers 256, -wal_files 0.\n> \n> FSYNC: 257tps\n> O_DSYNC: 333tps \n> \n> Just(?) 30% faster, -:(\n\nFirst of all, if you ask me, that is one hell of ... |
[
{
"msg_contents": "\n\n\nPeter Eisentraut writes:\n\n> Michal Maru�ka writes:\n\n> > What about (optionally) printing the type of the column data?\n\n> > io | tu | tipo | data\n> > int | int | int2 | date\n> > --------+-------+------+------------\n> > 102242 | 26404 | 1203 | 2000-11-22\n>... |
[
{
"msg_contents": "Hi Philip,\n\nI have not updated from CVS in a few days, but I suspect you haven't\nnoticed this yet: given a mixed-case table name and a scenario that\nrequires emitting UPDATE pg_class commands, pg_dump puts out\nthings like\n\nUPDATE \"pg_class\" SET \"reltriggers\" = 0 WHERE \"relname\" ~... |
[
{
"msg_contents": "but it's hard to notice eg misprints in 44K file -:)\nI think we should apply patches and hard test\nrecovering for a few days (power off/pg_ctl -m i stop\nwith dozens update transactions).\n\nVadim\n",
"msg_date": "Mon, 12 Mar 2001 15:57:55 -0800",
"msg_from": "\"Mikheev, Vadim\" <vm... |
[
{
"msg_contents": "> > FSYNC: 257tps\n> > O_DSYNC: 333tps \n> > \n> > Just(?) 30% faster, -:(\n> \n> First of all, if you ask me, that is one hell of an improvement :-)\n\nOf course -:) But tfsync tests were more promising -:)\nProbably we should update XLogWrite to write() more than 1 block,\nbut... |
[
{
"msg_contents": ">> > It is possible to build a logging system so that you \n>> > mostly don't care when the data blocks get written;\n>> > a particular data block on disk is considered garbage\n>> > until the next checkpoint, so that you\n>> >\n> > How to know if a particular data page was modified if there ... |
[
{
"msg_contents": "> > but it's hard to notice eg misprints in 44K file -:)\n> > I think we should apply patches and hard test\n> > recovering for a few days (power off/pg_ctl -m i stop\n> > with dozens update transactions).\n> \n> if this is the case, can we look at applying that patch \n> tonight, give ppl ti... |
[
{
"msg_contents": "There is another loose end that I forgot I needed to discuss with you.\n\nxlog.c's ReadRecord formerly contained code that would zero out the rest\nof the log segment (and delete the next log segment, if any) upon\ndetecting a missing or corrupted xlog record. I removed that code\nbecause I ... |
[
{
"msg_contents": "I wrote a couple days ago:\n\n: BTW, can we really trust checkpoint to mean that all data file changes\n: are down on disk? I see that the actual implementation of checkpoint is\n: \n: \twrite out all dirty shmem buffers;\n: \tsync();\n: \tif (IsUnderPostmaster)\n: \t\tsleep(2);\n: \tsync();... |
[
{
"msg_contents": "> I presume the point of this code was that if we recover and \n> then suffer\n> a later crash at a point where we've just written an xlog record that\n> exactly fills an xlog page, a subsequent scan of the log \n> might continue\n> on from that point and pick up xlog records from the prior (... |
[
{
"msg_contents": "> The more I think about this, the more disturbed I get. It seems clear\n> that this sequence is capable of writing out the checkpoint record\n> before all dirty data pages have reached disk. If we suffer a crash\n> before the data pages do reach disk, then on restart we will \n> not realiz... |
[
{
"msg_contents": "> > Should we try to read log up to the *physical end* - ie end of last\n> > log file - regardless invalid CRC-s/zero pages with attempt to\n> > re-apply interim valid records? (Or do we already do this?)\n> \n> That doesn't seem like a good idea --- once we fail to read an XLOG\n> record, it... |
[
{
"msg_contents": "\n> Anyway I like idea of StartUpID in page headers - this will help\n\nCan you please describe StartUpID for me ? \nIdeal would be a stamp that has the last (smallest open) XID, or something else \nthat has more or less timestamp characteristics (without the actual need of wallclock)\nin reg... |
[
{
"msg_contents": "I don't want to look a gift horse in the mouth, but it seems to me that the \nperformance monitor should wait until the now-famous query tree redesign \nwhich will allow for sets from functions. I realize that the shared memory \nrequirements might be a bit large, but somehow Oracle accomplis... |
[
{
"msg_contents": "The logical operators '&', '|', '<<' and '>>' as documented on the page\nhttp://www.postgresql.org/devel-corner/docs/postgres/functions.html don't\nappear to work as advertised.\n\ndarcy=# SELECT 91 & 15;\nERROR: Unable to identify an operator '&' for types 'int4' and 'int4'\n You wil... |
[
{
"msg_contents": "\nAre there plans to make 'createdb' support template0 before 7.1? If so,\nI'll amend backup.sgml...\n\n\n\n\n----------------------------------------------------------------\nPhilip Warner | __---_____\nAlbatross Consulting Pty. Ltd. |----/ - \\\n(A.B.N. 75 00... |
[
{
"msg_contents": "> > It will be tck/tk, so I guess X only.\n> \n> Good point. A typical DB server -- where is performance important -- \n> has install Xwin?\n> \n> BTW, I hate Oracle 8.x.x because has X+java based installer, but some\n> my servers hasn't monitor and keyboard let alone to Xwin.\n> \n> What ... |
[
{
"msg_contents": "\n> > > Anyway I like idea of StartUpID in page headers - this will help\n> > \n> > Can you please describe StartUpID for me ? \n> > Ideal would be a stamp that has the last (smallest open) XID, or something else \n> > that has more or less timestamp characteristics (without the actual need o... |
[
{
"msg_contents": "\n> > > StartUpID counts database startups and so has timestamp characteristics.\n> > > Actually, idea is to use SUI in future to allow reusing XIDs after startup: seeing\n> > > old SUI in data pages we'll know that all transaction on this page was committed\n> > > \"long ago\" (ie visible fr... |
[
{
"msg_contents": "As long as I'm about to change the xlog page headers, I have another\nlittle idea. Wouldn't it be a good idea to allow three backup pages\nper xlog record, not only two? It seems like three pages would be\na natural requirement for logging operations like index page splits.\n\nWe could supp... |
[
{
"msg_contents": "> >> xlog.c's ReadRecord formerly contained code that would zero \n> >> out the rest of the log segment (and delete the next log segment,\n> >> if any) upon detecting a missing or corrupted xlog record.\n> >> I removed that code because I considered it horribly dangerous\n> >> where it was. I... |
[
{
"msg_contents": "> As long as I'm about to change the xlog page headers, I have another\n> little idea. Wouldn't it be a good idea to allow three backup pages\n> per xlog record, not only two? It seems like three pages would be\n> a natural requirement for logging operations like index page splits.\n\nOn in... |
[
{
"msg_contents": "> >> What I was thinking about in that last paragraph was manual \n> >> analysis and recovery. I don't think it's a good idea for automatic\n> >> system startup to skip over gaps in the log.\n> \n> > But if we'll not try to read after gap then after restart \n> > system will not notice gap an... |
[
{
"msg_contents": "> > It will be sufficient if DB will not use all 2^32 XIDs \n> > without shutdown.\n> \n> I liked the xid wraparound idea, won't that be sufficient here too ?\n> I don't like the idea to reuse a xid sooner than absolutely necessary.\n\nWe need it to reduce pg_log size requirements.\n\n> This ... |
[
{
"msg_contents": "> > What I would refuse in the event of log corruption is continuing\n> > normal database operations.\n> \n> Hmm. We could do that if we had some notion of a read-only operating\n> mode, perhaps. But we don't have one now and I don't want to add it\n> for 7.1. Can we agree to look at this ... |
[
{
"msg_contents": "Can somone improve the wording?\n\n\tThe system is shutting down.\n\nwhen the backend receives a SIGTERM. Seems we need some wording that\ncan apply to db shutdown and individual backend termination by\nadministrators.\n\n-- \n Bruce Momjian | http://candle.pha.pa.us... |
[
{
"msg_contents": "\nHi,\n\nwhat's the postgresql equivalent of \n\nmysql_real_escape_string()\n\nto escape strings that are going to be passed to queries?\n\n(http://www.mysql.com/doc/n/o/node_641.html)\n\nThanks\n\nDaniel\n",
"msg_date": "Tue, 13 Mar 2001 12:44:35 -0800",
"msg_from": "Daniel Lopez <da... |
[
{
"msg_contents": "Hi Guys,\n\nI'd just like to point out that for most secure installations, X is\nremoved from servers as part of the \"remove all software which isn't\nabsolutely needed.\"\n\nI know of Solaris machines which perform as servers with a total of 19\nOS packages installed, and then precompiled b... |
[
{
"msg_contents": "contrib/pg_resetxlog is checked in. It's not really complete for the\ninteresting cases (ie, recovery from damaged files) but it does handle\nthe simple case of upgrading from 7.1beta5 to current sources.\n\nTo use: see contrib/pg_resetxlog/README.pg_resetxlog.\n\n\t\t\tregards, tom lane\n",... |
[
{
"msg_contents": "\n> > > It will be sufficient if DB will not use all 2^32 XIDs \n> > > without shutdown.\n> > \n> > I liked the xid wraparound idea, won't that be sufficient here too ?\n> > I don't like the idea to reuse a xid sooner than absolutely necessary.\n> \n> We need it to reduce pg_log size requirem... |
[
{
"msg_contents": "> > Peter Eisentraut <peter_e@gmx.net> writes:\n> > > \tThe connection was terminated.\n\n\tThe connection has been terminated. ??\n\n> > > And make the postmaster print out\n> > > \tThe system is shutting down.\n> > > before it sends out the SIGTERM's.\n\nI like above. Imho it is suffic... |
[
{
"msg_contents": "I have a server, with Postgres, and a squid running. The squid is a real \nCPU-mem eater, and in one of the inserts to the DB, I got this on the log \nfile and then the postmaster died.\n\n/dbs/postgres/bin/postmaster: reaping dead processes...\n/dbs/postgres/bin/postmaster: CleanupProc: pid ... |
[
{
"msg_contents": "> First day in week is Monday in ISO week.\n> Thomas, we have ISO week-of-year (IW in to_char or 'week' in date_part),\n> but we haven't ISO day-of-week (may be as 'ID' for to_char).\n> TODO for 7.2?\n> ..but in ISO is 0-6; 0=Mon\n\nI've been ignoring this until now, hoping no one would not... |
[
{
"msg_contents": "\n> Unix day-of-week starts on Sunday, not Monday, which is what\n> date_trunc('dow',...) returns. Presumably this is modeled on the\n> traditional notion (at least in the US; I suspect this is true in most\n> European countries at least) of Sunday being \"the first day of week\".\n\nGermany ... |
[
{
"msg_contents": "I would like to apply the following patch to the CVS tree. It allows\npgmonitor to show query strings even if the backend is not compiled with\ndebug symbols.\n\nIt does this by creating a global variable 'debug_query_string' and\nassigning it when the query begins and clearing it when the q... |
[
{
"msg_contents": "I'm running Postgres 7.0.3 on a RedHat Linux 6.1. For some reason, rtrim\nis giving me an incorrect result:\n\ndb01=# SELECT tablename FROM pg_tables WHERE tablename LIKE '%_opto' AND\n\ntablename NOT LIKE 'pg%' ORDER BY tablename ASC ;\n tablename\n-----------------\n center_out_opto\n c... |
[
{
"msg_contents": "We have an application that we were running quite happily using pg6.5.3\nin various customer sites. Now we are about to roll out a new version of\nour application, and we are going to use pg7.0.3. However, in testing\nwe've come across a couple of isolated incidents of database\ncorruption. T... |
[
{
"msg_contents": "Sorry, if I used not corresponding mailing list, but I really dont\nknow where to send such email.\n\nIs that possible to add one more SQL command to Postgres? The problem\nthat IMHO no one RDBMS allows SQL command for sheduling. To support\nsheduling SQL programmers have to use outer tools t... |
[
{
"msg_contents": "Hello all,\n\nI try to build postgresql 7.1 beta 5 on UnixWare 7.1.1. I have problem to\nbuild the Python extension,\nthere is a problem to build the shared library, I have see some information\non that but don't help me.\nSorry\n\nCan you help me by providing the correct command\n\nThanks\nJ... |
[
{
"msg_contents": "Hi all pgsql-hackers,\n\nIam a new hacker of this list.\n\nI and a few others have started an Linux localization project for Indian\nLanguages called - Project Tuxila (http://inapp.com/tuxila), and are\ncurrently doing the localization for an Indian language called\n\"Malayalam\". The utiliti... |
[
{
"msg_contents": "Based on the tests we did last week, it seems clear than on many\nplatforms it's a win to sync the WAL log by writing it with open()\noption O_SYNC (or O_DSYNC where available) rather than issuing explicit\nfsync() (resp. fdatasync()) calls. In theory fsync ought to be faster,\nbut it seems ... |
[
{
"msg_contents": "> Based on the tests we did last week, it seems clear than on many\n> platforms it's a win to sync the WAL log by writing it with open()\n> option O_SYNC (or O_DSYNC where available) rather than \n> issuing explicit fsync() (resp. fdatasync()) calls.\n\nI don't remember big difference in usin... |
[
{
"msg_contents": "\tI have started the \"PL/pgSQL CookBook\" project. The goal is to\ncreate a cookbook of PL/pgSQL functions that will be catalogued and made\navailable for others to use and learn from.\n\tCome to http://www.brasileiro.net/postgres and contribute your own \nPL/pgSQL (or PL/Tcl, PL/Perl) funct... |
[
{
"msg_contents": "> I believe that we don't know enough yet to nail down a hard-wired\n> decision. Vadim's idea of preferring O_DSYNC if it appears to be\n> different from O_SYNC is a good first cut, but I think we'd \n> better make it possible to override that, at least for testing purposes.\n\nSo let's leav... |
[
{
"msg_contents": "I have completed all the features I want in the first release of\npgmonitor. It is available at:\n\n\tftp://candle.pha.pa.us/pub/postgresql/pgmonitor.tar.gz\n\nI am going to send this over soon to announce/general to encourage its\nuse.\n\n-- \n Bruce Momjian | http:... |
[
{
"msg_contents": "Tom Lane wrote:\n> Jan Wieck <janwieck@Yahoo.com> writes:\n> > What about a collector deamon, fired up by the postmaster and\n> > receiving UDP packets from the backends. Under heavy load, it\n> > might miss some statistic messages, well, but that's not as\n> > bad as having... |
[
{
"msg_contents": "Tom Lane wrote:\n> Jan Wieck <janwieck@Yahoo.com> writes:\n> > What about a collector deamon, fired up by the postmaster and\n> > receiving UDP packets from the backends. Under heavy load, it\n> > might miss some statistic messages, well, but that's not as\n> > bad as having... |
[
{
"msg_contents": "\n\tI have started the \"PL/pgSQL CookBook\" project. The goal is to\ncreate a cookbook of PL/pgSQL functions that will be catalogued and made\navailable for others to use and learn from.\n\tCome to http://www.brasileiro.net/postgres and contribute your own \nPL/pgSQL (or PL/Tcl, PL/Perl) fun... |
[
{
"msg_contents": "I have written a simple search engine that utilizes pgsql. I would\nlike to make it a stored procedure, although I am still learning\nplpgsql. Attached to this message is the basic search logic (in PHP).\nThis script will be in production on a major e-commerce site in about\na week. I thin... |
[
{
"msg_contents": "begin 644 searchraw.php3\nM/#]P:'`*\"2\\O<W1A<G0@<V5S<VEO;@H)\"7-E<W-I;VY?<W1A<G0H*3L*\"2\\O\nM<&%R<V4@:6YP=70*\"0DD8VQE86Y?<75E<GD@/2!T<FEM*'-T<G1O=7!P97(H\nM)&-R:71E<FEA*2D[\"@DO+VUA:V4@87)R87D*\"0DD87)R87E?;V9?=V]R9',@\nM/2!E>'!L;V1E*\"<@)RP@)&-L96%N7W%U97)Y*3L*\"2\\O82!L:7-T(&]F('-T\nM;W`... |
[
{
"msg_contents": "\nI know there are still discussions going on concerning the whole fsync\nissue, but, from what I've been following, its purely a performance issue\nthen anything ...\n\nNow that Tom's patch is in place for the XLOG stuff, I'd like to put out a\nBeta6 tomorrow for testing, with an RC1 schedua... |
[
{
"msg_contents": "Greetings,\n\n I'm getting errors as a result of making queries. The attached log from \nthe last two queries gives an idea as to what is happening.\n\n I suspect I must have done something bad when I upgraded via cvsup.\n\n Does this mean that I should do an initdb?\n\n-- \nSincerely etc.... |
[
{
"msg_contents": "\n> Okay ... we can fall back to O_FSYNC if we don't see either of the\n> others. No problem. Any other weird cases out there? I think Andreas\n> might've muttered something about AIX but I'm not sure now.\n\nYou can safely use O_DSYNC on AIX, the only special on AIX is,\nthat it does not ... |
[
{
"msg_contents": "> > I was wondering if the multiple writes performed to the \n> > XLOG could be grouped into one write().\n> \n> That would require fairly major restructuring of xlog.c, which I don't\n\nRestructing? Why? It's only XLogWrite() who make writes.\n\n> want to undertake at this point in the cycle... |
[
{
"msg_contents": "> We've speculated about using Posix semaphores instead, on platforms\n\nFor spinlocks we should use pthread mutex-es.\n\n> where those are available. I think Bruce was concerned about the\n\nAnd nutex-es are more portable than semaphores.\n\nVadim\n",
"msg_date": "Fri, 16 Mar 2001 09:10... |
[
{
"msg_contents": "> >> definitely need before considering this is to replace the existing\n> >> spinlock mechanism with something more efficient.\n> \n> > What sort of problems are you seeing with the spinlock code?\n> \n> It's great as long as you never block, but it sucks for making things\n\nI like optimist... |
[
{
"msg_contents": "\n> For a log file on a busy system, this could improve throughput a lot--batch\n> commit. You end up with fewer than one fsync() per transaction.\n\nThis is not the issue, since that is already implemented.\nThe current bunching method might have room for improvement, but\nthere are current... |
[
{
"msg_contents": "My problem is that my two outer joined tables have columns that have the \nsame names. Therefore when my select list tries to reference the \ncolumns they are ambiguously defined. Looking at the doc I see the way \nto deal with this is by using the following syntax:\n\ntable as alias (colum... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.