threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "With the freshly retrieved current source, now PostgreSQL is running\nfine on an AIX 5L box. Thanks Tom.\n\nBTW, I have done some benchmarking using pgbench on this machine and\nfound that 7.2 is almost two times slower than 7.1. The hardware is a\n4way machine. Since I thought that 7.2 impro... |
[
{
"msg_contents": "Marc, can we increase the size of messages allowed on the patches list? \nI am getting complaints about delays, and I keep the patches 1-2 days\nbefore being applied too.\n\nPeople are starting to try and bypass the limit by posting URL's or\nsending emails directly to me; neither seems good... |
[
{
"msg_contents": "Tom writes:\n> Peter Eisentraut <peter_e@gmx.net> writes:\n> > Zeugswetter Andreas SB SD writes:\n> >> Second I do not understand why the Makefile in pl/tcl is so complicated,\n> >> and not similar e.g. to the plpython one, so the first task should be to\n> >> simplify the Makefile to use Mak... |
[
{
"msg_contents": "Apparently there's been a change in the way views are handled within \nPL/pgSQL. The following program works fine in earlier versions of \nPostgreSQL. It also works if the select on the view is replaced with a \ndirect call to nextval().\n\nWe use this construct repeatedly in OpenACS so we ... |
[
{
"msg_contents": "Is there any reason why recursive SQL functions are not allowed in PG 7.2?\n\nAfter all this:\n\ncreate function foo() returns setof integer as 'select 1'\nlanguage 'sql';\n\ncreate or replace function foo() returns setof integer as\n'select foo()'\nlanguage 'sql';\n\nWorks fine ...\n\nIt tur... |
[
{
"msg_contents": "\nGot a report the other day of a \"problem\" with pg_dump where, if in the\nmiddle of a dump, someone happens to drop a table, it errors out with:\n\n SQL query to dump the contents of Table 'server_2' did not execute.\nExplanation from backend: 'ERROR: Relation 'server_2' does not e... |
[
{
"msg_contents": "Apparently there's been a change in the way views are handled within \nPostreSQL. The following program works fine in earlier versions. It \nalso works if the select on the view is replaced with a direct call to \nnextval().\n\nWe use this construct repeatedly in OpenACS so we can share que... |
[
{
"msg_contents": "Is there any reason why recursive SQL functions are not allowed in PG 7.2?\n\nAfter all this:\n\ncreate function foo() returns setof integer as 'select 1'\nlanguage 'sql';\n\ncreate or replace function foo() returns setof integer as\n'select foo()'\nlanguage 'sql';\n\nWorks fine ... (until yo... |
[
{
"msg_contents": "I was browsing through the TODO list and stumbled upon the connection pooling \nitem discussed over a year ago. Is it safe to assume that since it's still \nlisted in the TODO that it's still a desirable feature? Although I don't know \nclaim to know jack about the postgresql source (although... |
[
{
"msg_contents": "I have observed a nasty three-way deadlock condition.\n\nThis proc is trying to generate a new transaction ID, and has hit the one\ncase in every 32K where a new page must be added to the CLOG. That\nmeans that an XLOG record must be written to record the creation of the\nnew CLOG page:\n\nU... |
[
{
"msg_contents": "I have just run 7.2b4 on FreeBSD/alpha.\n\nThe float8 and geometry tests failed.\n\nAttatched is the regression stuff. I have submitted it to the database.\n\nI'm not certain how significant the results are.\n\nEspecially these ones:\n\n--- 241,249 ----\n INSERT INTO FLOAT8_TBL(f1) VALUES (... |
[
{
"msg_contents": "Hi,\n\nI am a new to Postgres. I have a problem. I want to\nschedule some jobs at a particular time on a\nparticular day of a week. To make it more clear, my\nrequirement is to send mails to people based on the\navailability of data in some fields once in every\nweek. How do I go about doing ... |
[
{
"msg_contents": "I haven't tested with the new 7.2 betas, but here are some results from\n7.1.\n\nWe have a developement computer, IBM x series 250, with 4 processors\n(PIII Xeon 750Mhz), 1 Gb memory and 2SCSI disks (u160).\n\nThe software is writing new rows to a table, and after this it reads the\nid from ... |
[
{
"msg_contents": "> \"Zeugswetter Andreas SB SD\" <ZeugswetterA@spardat.at> writes:\n> > Here is a patch per above thread.\n> \n> Why did you change libpgtcl's build process? AFAIK no one was claiming\n> that was broken.\n\nIt was definitely broken on AIX, and was also the original complaint.\nSince the make ... |
[
{
"msg_contents": "I feel there was a reasonably nice client side attempt at this using a\nworker pool model or something. Can't seem to track it down at this moment.\nAlso would spread queries in different ways to get a hot backup equivalent\netc. It was slick.\n\nThe key is that pgsql be able to support a ver... |
[
{
"msg_contents": "I know I have expressed these concerns before but lost the argument, or\nat least no one rallied to my position, but I feel I have to mention\nthese again because they came up during beta.\n\nMy first concern is that VACUUM now defaults to the non-locking version.\nWhile I appreciate the new ... |
[
{
"msg_contents": "Hi,\nI got this patch working on 7.2b4, uses locale setting for input/output \nnumeric datatype.\nIt do not modify the regression tests.\n\nAny suggestion on How is implemented ?\nHow to change the regression test, to make it work on all the locale \nsettings ?\n\nthanks\nGiuseppe\n\n\n-- \n... |
[
{
"msg_contents": "> However, there's still a problem: GetUndoRecPtr also gets SInvalLock\n> while its caller holds WALInsertLock, and therefore this routine\n> could create the second leg of the deadlock too. Removing the\n> SInvalLock lock there creates the problem that backends might be\n> added to or delet... |
[
{
"msg_contents": "> > Checkpoint' undo is not used currently so just comment out \n> > GetUndoRecPtr call in CreateCheckPoint - we'll find solution later.\n> \n> I thought about that, but figured you'd object ;-)\n> \n> One possibility is to do something you had recommended awhile back for\n> other reasons: ad... |
[
{
"msg_contents": "> This is trying to get rid of the original copy of a tuple that's been\n> moved to another page. The problem is that your index \n> function causes a\n> table scan, which means that by the time control gets here, \n> someone else\n> has looked at this tuple and marked it good --- so the ini... |
[
{
"msg_contents": "> > Looks like we have to add checks for the case\n> > TransactionIdIsCurrentTransactionId(tuple->t_cmin) when\n> > there is HEAP_MOVED_OFF or HEAP_MOVED_IN in t_infomask to\n> > all HeapTupleSatisfies* in tqual.c as we do in\n> > HeapTupleSatisfiesDirty - note comments about uniq btree-s the... |
[
{
"msg_contents": "After reading through the strong opinions about the location of the\nconfiguration files in the current and in previous threads, I must concede\nthat despite the best intentions, the current \"everything in one place\"\nsystem is obviously not addressing the needs of the user. So while we're... |
[
{
"msg_contents": "In the vacuum tuple-chain moving logic, shouldn't the lines that update\nthe new tuple's t_ctid (vacuum.c lines 1882-1891 in current sources)\nbe moved up to before the log_heap_move call at line 1866?\n\nIt appears to me that as the code stands, log_heap_move will log the new\ntuple containi... |
[
{
"msg_contents": "I was wondering, when we start to reuse a WAL file, do we know that all\ndirty buffers modified in that WAL file have been flushed to disk? Do\nwe fsync() dirty buffers at time of checkpoint, and do we also make sure\nthat buffers we wrote to disk and later reused before the checkpoint\nalso... |
[
{
"msg_contents": "Hello,\nI found the following code in postgresql-7.2b4/src/interfaces/perl5/Pg.pm:101 file.\n\n$Pg::VERSION = '1.9.0';\n\nIs this version number correct? I think this version is 1.8.X.\nThe latest release of pgsql_perl5 is also 1.9.0. And we can find the following url.\n\nhttp://search.cpan.o... |
[
{
"msg_contents": "Hi,\nI got this patch working on 7.2b4, uses locale setting for input/output\nnumeric datatype.\nIt do not modify the regression tests.\n\nAny suggestion on How is implemented ?\nHow to change the regression test, to make it work on all the locale\nsettings ?\n\nthanks\nGiuseppe\n\n\n-- \n--... |
[
{
"msg_contents": "\n\n> -----Original Message-----\n> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us] \n> Sent: 19 December 2001 02:07\n> To: Thomas Swan\n> Cc: Peter Eisentraut; PostgreSQL Development\n> Subject: Re: Thoughts on the location of configuration files\n> \n> \n> > >I suggest that we wire-in t... |
[
{
"msg_contents": "\n> > > Here is a patch per above thread.\n> >\n> > Why did you change libpgtcl's build process? AFAIK no one was claiming\n> > that was broken.\n> >\n> > This does not seem the right time to be making undiscussed changes in\n> > Makefile.shlib, either. What's with that?\n> \n> I wasn't und... |
[
{
"msg_contents": "\n> I think the data directory should be explicitly configured by either the\n> posgresql.conf file, environment variable (PGDATA), or through the command line\n> option, but using the \"configure\" statedir isn't anything \n> anyone would object too.\n\nChanging the default data location at ... |
[
{
"msg_contents": "> I think you are right that the difference between 7.1 and 7.2 may have\n> more to do with the change in VACUUM strategy than anything else. Could\n> you retry the test after changing all the \"vacuum\" commands in pgbench.c\n> to \"vacuum full\"?\n\nMight there also be a difference in chos... |
[
{
"msg_contents": "\n> > Changing the default data location at this point would imho \n> > be a major hassle for those actually using the default.\n> > Thus I object to changing it.\n> \n> The idea is to have the default configuration file location \n> possible to change at configure time.\n\nI totally suppo... |
[
{
"msg_contents": "I've just installed 7.2b4 on Irix modifications works perfectly.\noffsetof works properly\nMy apologizes for the long time.\nRegards\nLuis Amigo\nProfiling must wait for a while\n\n\n",
"msg_date": "Wed, 19 Dec 2001 18:25:22 +0100",
"msg_from": "Luis Amigo <lamigo@atc.unican.es>",
... |
[
{
"msg_contents": "Hi,\n\nI was installing the ODBC driver on an alpha box. Problem is that there \nare assumptions in the typedefs that a four byte integer is a \"long \nint\". Of course, this is often an incorrect assumption. I can fix this, \nbut wanted to know how people wanted this done. How do you han... |
[
{
"msg_contents": "I'd like to claim that these will be removed from the parser in the next\nrelease (7.3). Any objections? I had thought to advocate removing them\nnow, but decided the outcome of the discussion isn't worth the\ndiscussion itself at the moment ;)\n\nComments? I'm updating the docs to reflect \"... |
[
{
"msg_contents": "\n See:\n\n./configure --prefix=/usr/lib/postgresql \\\n --with-unixodbc \\\n --enable-odbc \\\n --with-openssl \\\n --with-pam \\\n --with-python \\\n --with-perl \\\n --with-tcl \\\n... |
[
{
"msg_contents": "\n Hi,\n\n on system without perl-dev the ./configure --with-perl pass without\n some error message and error appear during compilation:\n\n LD_RUN_PATH=\"\" cc -shared -L/usr/local/lib plperl.o eloglvl.o SPI.o -L/usr/local/lib /usr/lib/perl/5.6.1/auto/DynaLoader/DynaLoader.a -L/usr/lib/perl... |
[
{
"msg_contents": "A quick search of the source code and archives failed to show \nanything related to this (which may reflect my searching skills \nmore than anything else), so I'll toss it out here as a wishlist\nitem. \n\nWishlist: TLS (SSL) authentication\n----------------------------------\n\nWhile superf... |
[
{
"msg_contents": "Where are we on the RC1 release? What are the open items? I have\ngotten lost.\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, | 830 Blythe Avenue\n + Christ can be... |
[
{
"msg_contents": "> If \"pre-page WAL write\" means the value of the page before the current\n> changes, then there is generally another reason for writing it out.\n\nBruce, \"*pre*-page\" is confusing - we write \"after-change\" page\nimage to WAL.\n\n> When the system comes back up, we need to do a rollback ... |
[
{
"msg_contents": "I wrote two functions I think are quite cool.\n\nint_aggregate_array(int)\nand\nint_enum_array(int[])\n\n\nWhile I'm not sure I can submit them because I wrote them on company\ntime, I thought I should tell you about them because they are fairly\ntrivial, and could make postgresql better.\n\n... |
[
{
"msg_contents": "Hi All,\n\nYou know how when you create a foreign key in postgres it isn't\nautomatically indexed, and it seems to me that it's very useful to have\nindexed foreign keys, especially if you use lots of them.\n\nSo, how about a 'findslowfks' contrib? This would basically be similar to\nBruce's... |
[
{
"msg_contents": "In HEAD contrib/dbase:\n\ngcc -pipe -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../src/\ninterf\naces/libpq -I. -I../../src/include -c -o dbf2pg.o dbf2pg.c\ndbf2pg.c:19: iconv.h: No such file or directory\ndbf2pg.c:38: syntax error before `iconv_d'\ndbf2pg.c:38: warning: type... |
[
{
"msg_contents": "Hi Marko,\n\nJust testing pgcrypto on freebsd/alpha. I get some warnings:\n\ngcc -pipe -O -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -DPIC \n-DRAND_SILLY -I. -I. -I../../src/include -c -\no internal.o internal.c\ninternal.c: In function `rj_encrypt':\ninternal.c:314: warning... |
[
{
"msg_contents": "\n> > If you have a foreign key on a column, then whenever the primary key is\n> > modified, the following checks may occur:\n> > \n> > * Check to see if the child row exists (no action)\n> > * Delete the child row (cascade delete)\n> > * Update the child row (cascade update)\n> > \n> > All o... |
[
{
"msg_contents": "I just looked at the source for dbase. I have a long hacked version of\nthis. The one in contrib is based on a newer version of what I have been\nusing.\n\nIt is funny, because I made some of the same changes to mine as are in\nthe one in contrib, with a few exceptions.\n\nusage: dbf2pg [opt... |
[
{
"msg_contents": "I've said it before, the HISTORY file really contains a lot of inaccurate\ninformation, not to say nonsense. Plus, I find the sectioning and sorting\nto be pretty peculiar.\n\nSo I've tried to give it some better structure, correct the mistakes,\nimprove spelling, and convert it to DocBook i... |
[
{
"msg_contents": "has the default clause been changed for 7.2b4 so as not use a statement as such:\n\ncreate table news(\nid serial,\ndate date DEFAULT 'select now()::date' NOT NULL,\ntopic varchar(256),\nbody text\n);\n\nthe above query results in ERROR: Bad date external representation 'select now()::date',... |
[
{
"msg_contents": "Hi,\n\nI just fixed some nasty bugs in ecpg, especially when it comes to using\narrays of structs. It seems this feature has never been fully implemented.\nDuring my search for these bugs I also fixed some other including one memory\nrelated one. \n\nAfter all I had to make changes in quite s... |
[
{
"msg_contents": "I am pleased to announce the initial release of \"libpkixpq\", \nPostgreSQL user-defined types and functions that allow the\ndatabase to understand the basic PKIX types. \n\nThis release should be considered EXPERIMENTAL. This is \nliterally the first public release and the lack of known\nb... |
[
{
"msg_contents": "hello pgsql-hackers,\n\nI'm very very very... new here, but...\nWell, I see you're all stressed by the new release comming up soon, but may\nbe one of you guys has got an ear and a couple of words for a smb who really\nwants to get involved.\n\nme: I think, I've got enough programming experie... |
[
{
"msg_contents": "Hi, \n\nI just felt on this one :\n\ncreate table radlog (\n...\ndebut timestamp,\nfin timestamp,\n...)\n\nselect extract(YEAR FROM debut) as annee,extract(MONTH FROM debut) as\nmois, EXTRACT(EPOCH FROM sum(fin-debut)) as total, EXTRACT(EPOCH FROM\navg(fin - debut)) from radlog where fin is n... |
[
{
"msg_contents": "On Mon, 24 Dec 2001, Thomas Lockhart wrote:\n\n> (resent due to dns trouble)\n> \n> > select extract(YEAR FROM debut) as annee,...\n> > EXTRACT(EPOCH FROM avg(fin - debut))\n> > from radlog where fin is not null;\n> > Fails with '0' bas interval external representation for any debut = fin.\n>... |
[
{
"msg_contents": "For those who're celebrating it now,\nfor those it has passed a few hours ago and\nfor those it will come in a few hours ---\n\n Merry Christmas\n Joyeux No�l\n Feliz Navidad\n\n!!!\n\n--\nSerguei A. Mokhov\n\n\n",
"msg_date": "Mon, 24 Dec 2001 18:52:29 -0500",
"msg_from": ... |
[
{
"msg_contents": "I found a failure in a JDBC driver of 7.2b4.\n (1) It does not support timestamptz type\n (2) Exception occurs by timestamp without time zone type\nI attach a patch correcting the first failure.\nYou can confirm it in example.psql as follows:\n\n---------------------------------------------... |
[
{
"msg_contents": "Lamar Owen writes:\n\n> Why isn't all of it in postgresql.conf?\n\nBecause the postgresql.conf and pg_hba.conf files describe different data\nstructures that are evaluated at different times in different ways for\ndifferent reasons.\n\n-- \nPeter Eisentraut peter_e@gmx.net\n\n",
"msg_da... |
[
{
"msg_contents": "Someone reported to me that they can't get their queries to use indexes.\nIt turns out this is because timestamp() has pg_proc.proiscachable set\nto false in many cases. Date() also has this in some cases.\n\nI realized timestamp() can be called with 'CURRENT_TIMESTAMP', which of\ncourse is ... |
[
{
"msg_contents": "> Someone reported to me that they can't get their queries to use indexes.\n> It turns out this is because timestamp() has pg_proc.proiscachable set\n> to false in many cases. Date() also has this in some cases.\n\nPlease let me add a reference to this email from Tom Lane:\n\n\thttp://fts.po... |
[
{
"msg_contents": "\nBased on Tom's comments and this email, I am adding this to the TODO\nlist:\n\n* Add new pg_proc cachable settings to specify whether function can be\n evaluated only once or once per query\n\n\n---------------------------------------------------------------------------\n\n> > Someone repo... |
[
{
"msg_contents": "A quote from backend's po:\n\n> #: ../access/nbtree/nbtinsert.c:552\n> #, c-format\n> msgid \"\"\n> \"_bt_getstackbuf: my bits moved right off the end of the world!\\n\"\n\nShould I feel free in translating this, Bruce? ;)\n\n--\nSerguei A. Mokhov\n \n\n",
"msg_date": "Wed, 26 Dec 2001 1... |
[
{
"msg_contents": "I have a /data directory from someone running 7.1.3 and they are seeing\ndata corruption on a table using TOAST columns. Specifically, they are\nseeing this:\n\t\n\ttest=> SELECT woman FROM user_details WHERE uid = '00eezEoLyWJK';\n\tERROR: Relation 1 does not exist\n\n\ttest=> SELECT quest... |
[
{
"msg_contents": "hello hackers\n\nhere is the patch for the INSERT INTO t VALUES (..., DEFAULT, ...) from the\ncurrent TODO list.\nIt's my first patch so please forgive me if it's not the best solution - I'm\nnow learning about the codebase and this implementation really hunted me\nthrough some deep and dark ... |
[
{
"msg_contents": "I've seen a few postings in multiple newsgroups saying that in 7.1.x and \nup, literals in SQL statements are implicitly cast to strings.\n\nFor example in:\nselect distinct 'hello' from mytable;\nthe 'hello' is implicitly assumed to be 'hello'::text\n\nHowever, in both 7.1.3, and a fresh bui... |
[
{
"msg_contents": "what is meant by the TODO-item \"Disallow missing columns in INSERT ...\nVALUES, per ANSI\" ?\n\nrgds\nPavlo Baron\n\n",
"msg_date": "Thu, 27 Dec 2001 21:58:06 +0100",
"msg_from": "\"Pavlo Baron\" <pb@pbit.org>",
"msg_from_op": true,
"msg_subject": "TODO question"
},
{
... |
[
{
"msg_contents": "This TODO-item \"SELECT col FROM tab WHERE numeric_col = 10.1 fails, requires\nquotes\" - is it already fixed? I executed smth. like\n\nselect * from tab2 where dpcol = 10.1;\n\nand it returns a record containing this value in the double precision column\n\"dpcol\".\n\nrgds\nPavlo Baron\n\n",... |
[
{
"msg_contents": "These things look like bugs to me:\n\nheap_xlog_clean doesn't update the page's LSN and SUI.\n\nheap_xlog_insert and heap_xlog_update leave random bits in the\ninserted/updated tuple's t_ctid. heap_xlog_update leaves random\nbits in the updated tuple's t_cmax in the \"move\" case.\n\nI am no... |
[
{
"msg_contents": "Hi All,\n\nHas anyone used pltclu in postgres (version 7.1, on\nLinux 7.1). I wanted to use a function called pgmail\nwritten in pltclu. But i am not able to create that\nfunction in postgres as the language pltclu is not\ncreated. I tried to create the language pltclu, but\ncouldnt succeed a... |
[
{
"msg_contents": "I got this error from JDBC driver which performing a\nupdate. Does\nanyone knows what cause it? I am using Postgre 7.1.3\nand its JDBC\ndriver.\n\nThanks,\nKevin\n\n\n\n__________________________________________________\nDo You Yahoo!?\nSend your FREE holiday greetings online!\nhttp://greetin... |
[
{
"msg_contents": "For 7.2, to support some ISO-8601 variants, I'm tightening up the date\ndelimiter parsing to require the same delimiter to be used between all\nparts of a date.\n\nDoes anyone use the German date notation for PostgreSQL? If so, what is\nthe actual format you input? The reasons I'm asking are:... |
[
{
"msg_contents": "Hi all!\n\nI have an Access 2000 database (under Windows 2000) which has tables linked\nfrom a PostgreSQL database. These tables have been linked using the\nPostgreSQL ODBC driver 7.01.0004 or some version around that (sorry, I don't\nremember the exact version). The Access ODBC connect strin... |
[
{
"msg_contents": "I've committed changes to tighten up the date/time parsing, while\nenabling more edge cases which should have worked but didn't. The\nchanges have the following effects:\n\n1) date fields like \"2001-12-29\" need the same delimiter between all\nfields. Previously, any of \"-\", \"/\", or \".\... |
[
{
"msg_contents": "After some further experimentation, I believe I understand the reason for\nthe reports we've had of 7.2 producing heavy context-swap activity where\n7.1 didn't. Here is an extract from tracing lwlock activity for one\nbackend in a pgbench run:\n\n2001-12-29 13:30:30 [31442] DEBUG: LWLockAc... |
[
{
"msg_contents": "How does PG handle DDL statements that are wrapped in a transaction?\nDoes it roll them back if one fails, or is it like Oracle?\n\nWhere is this documented?\n\nThanks.\n",
"msg_date": "29 Dec 2001 13:12:27 -0800",
"msg_from": "james@unifiedmind.com (James Thornton)",
"msg_from_op... |
[
{
"msg_contents": "make[3]: Entering directory `/home/postgres/pgsql/src/backend/parser'\ngcc -O1 -Wall -Wmissing-prototypes -Wmissing-declarations -g -I../../../src/include -c -o analyze.o analyze.c\nIn file included from analyze.c:23:\n../../../src/include/parser/parse.h:160: warning: `TIME' redefined\n../.... |
[
{
"msg_contents": "This article explains the value of a constent coding style:\n\n\thttp://ezine.daemonnews.org/200112/single_coding_style.html\n\nI have added a link from the developer's FAQ.\n\n-- \n Bruce Momjian | http://candle.pha.pa.us\n pgman@candle.pha.pa.us | (6... |
[
{
"msg_contents": "Presently, the RESUME_INTERRUPTS() and END_CRIT_SECTION() macros implicitly\ndo a CHECK_FOR_INTERRUPTS(); that is, if a cancel request arrived during\nthe interrupt-free section it will be serviced immediately upon exit\nfrom the section.\n\nIt strikes me that this is a really bad idea. Ther... |
[
{
"msg_contents": "Hi all!!\n\nI'm testing 7.2b4 and I have this (little problem) when importing the\n7.1.3 databases:\n\n2 of the databases are owner by a gone user (not in the system\nanymore) That gives errors when recreating databases.\n\nI'd like to see this databases belong to me (that one was easy : cha... |
[
{
"msg_contents": "On 12/22/2001 12:50:08 AM Bruce Momjian wrote:\n> > Who contributed it? Did Maarten Boekhold? I would like to merge my \ndata\n> > type and table prefix code into the main tree, if this is where it \nwill\n> > now be officially maintained.\n> \n> contrib/README shows:\n> \n> dbase -\n> ... |
[
{
"msg_contents": "\n\nThe one variant I'd like it to accept is 'yyyy-mm-ddThh:nn:ss', as in\n'2001-12-31T13:30:46'. This is the ISO-8601 format that perl's Time::Piece and I\nthink at least one other perl date module use as their 'standard ISO' output\nformat, and the default format that's closest to what Post... |
[
{
"msg_contents": "Happy New Year\n\n\tRegards,\n\t\tOleg\n_____________________________________________________________\nOleg Bartunov, sci.researcher, hostmaster of AstroNet,\nSternberg Astronomical Institute, Moscow University (Russia)\nInternet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/\nphone: +007(0... |
[
{
"msg_contents": "Just wishing a Marvelous New Year :)\n\nLet this year be a bit more luckier for everyone\ncompared to the previous one!\n\n--\nSerguei A. Mokhov\n \n\n",
"msg_date": "Mon, 31 Dec 2001 14:36:05 -0500",
"msg_from": "\"Serguei Mokhov\" <sa_mokho@alcor.concordia.ca>",
"msg_from_op": ... |
[
{
"msg_contents": "Happy new year to all of you.\n\nMay this year give a lot to you AND postgresql!!!\n\nRegards to you all\n\n-- \nOlivier PRENANT \tTel:\t+33-5-61-50-97-00 (Work)\nQuartier d'Harraud Turrou +33-5-61-50-97-01 (Fax)\n31190 AUTERIVE +33-6-07-63-80-64 (GSM)\n... |
[
{
"msg_contents": "Happy new year for all!\n\nI would like to tell you about the results of my work on pl/j.\nmemo: Java and postgres must run in a separate address space. First I \nwanted to use the sys v ipc, which was a bad idea becouse of some \nproblems with java VM-s. Many hackers told me about its bad si... |
[
{
"msg_contents": "Dear all,\n\nI wish you all a happy new year.\nThanks again for working on PostgreSQL\n\nBest regards,\nJean-Michel POURE\n",
"msg_date": "Tue, 1 Jan 2002 14:59:54 +0100",
"msg_from": "Jean-Michel POURE <jm.poure@freesurf.fr>",
"msg_from_op": true,
"msg_subject": "Happy new ye... |
[
{
"msg_contents": "I have found a case in nbtree where it is possible for two concurrent\ntransactions to insert the same key value in a unique index :-(\n\nThe reason is that _bt_check_unique can (of course) only detect keys\nthat are already in the index. To prevent concurrent insertion of\nduplicate keys, w... |
[
{
"msg_contents": "\tSo I discovered today that pgdb follows in the traditional style of\ncarrying timestamp and most other time fields through to the user as\ntext strings, so I either need to have all my queries do some gymnastics\nto have the server format my time information in a way that is printable\nor c... |
[
{
"msg_contents": "Over the last two days I have been struggling with running vacuum on a \n7.2b4 database that is running in a production environment. This was \nessentially the first time I ran vacuum on this database since it was \nupgraded to 7.2. This database is characterized by one large table that \nh... |
[
{
"msg_contents": "Hi, I'm new to this list.\n\nHaving got some insight into the PostgreSQL sources by following\nserver action using GDB and after trying to implement some features I\nbecame able to formulate a proposal which IMHO could be useful for\nothers, too.\n\nThe proposal consists in generalizing the P... |
[
{
"msg_contents": "\n Hi,\n\n I start fix my bug with \"YY vs. zero\" in formatting.c, and before it\n a see current CVS:\n\ntest=# select to_timestamp('10-10-2001', 'MM-DD-YYYY');\n to_timestamp\n------------------------\n 2001-10-10 00:00:00+02\n(1 row)\n\ntest=# select to_date('10-10-2001', 'MM-DD-YYYY'... |
[
{
"msg_contents": "\nHow do you people look at various trees and lists when debugging them ?\n\nDo you \n\n1. use functions from nodes/print.c to print out tree snapshots\n\n2. run the backend under visual debugger (like DDD) and look at things\nthere\n\n3. memorize everything in binary and work on raw memory i... |
[
{
"msg_contents": "\nWe are running the 7.2b4 beta server.\n\nThis join worked last week and today it gets and error:\n\nselect * from b, d\n where b.address = d.address;\n\nIt now fails with the following error:\nERROR: join_selectivity: bad value -0.121693\n\nall that is in the pgsql.log file is the same err... |
[
{
"msg_contents": "\nA question came up on the jdbc mail list today that I couldn't answer. \nIt involves some code that is in the jdbc cvs tree (and has been for \nmany releases). This code contains the following license terms in each \nfile:\n\n/*\n* Redistribution and use of this software and associated doc... |
[
{
"msg_contents": "Okay, I've been able to reproduce the problem here. Looks like the\neqjoinsel math is not wrong, exactly, but small roundoff errors are\ncausing the logic to do unreasonable things. I think\nget_att_numdistinct needs to round its result to an integer, and\nprobably there needs to be some cl... |
[
{
"msg_contents": "\nOK, can someone comment on this email I received. I am confused myself.\nFAQ item 4.1 says:\n\n> 4.1) Why is system confused about commas, decimal points, and date formats.\n\nDoes locale only control dates? If so, why the mention of commas? This\nitem was there before I started maintain... |
[
{
"msg_contents": "TODO: I have added a syntax suggested by someone on IRC:\n\n* Make it easier to create a database owned by someone who can't createdb,\n perhaps CREATE DATABASE dbname WITH USER = \"user\"\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\n-- \n Bruce Momjian |... |
[
{
"msg_contents": "> Tatsuo, is AIX capable of <10 millisecond sleeps?\n\nYes, the select granularity is 1 ms for non root users on AIX.\n\nAIX is able to actually sleep micro seconds with select\nas user root (non root users can use usleep for the same \nresult). AIX also has yield.\n\nI already reported this ... |
[
{
"msg_contents": "Hi,\n\nI am doing some tests with functions in 7.2b4. I got some stuff to work \nthat returns 'setof text' but I was wondering whether it is possble to let \nthe function return more than one column, something like:\n\ncreate function myfunc (integer) returns setof (text, integer)\n\nor\n\ncr... |
[
{
"msg_contents": "Shahid Mohammad Shamsi (mshamsi@dinmar.com) reports a bug with a severity of 2\nThe lower the number the more severe it is.\n\nShort Description\nselect table privilege in postgres allows user to create index on the table\n\nLong Description\nI created a user and assigned select privilege on... |
[
{
"msg_contents": "Look at this:\n\n\t$ dropdb lijasdf oiuwqe test\n\tDROP DATABASE\n\nThe create/drop scripts only process the last arguments, ignoring\nearlier ones. I assume no one wants me to fix it now so I will add this\nto TODO:\n\n\t* Prevent create/drop scripts from allowing extra args (Bruce)\n\n-- \... |
[
{
"msg_contents": "> > Bruce Momjian <pgman@candle.pha.pa.us> writes:\n> > > Seems nested transactions are not required if we load\n> > > each COPY line in its own transaction, like we do with\n> > > INSERT from pg_dump.\n> > \n> > I don't think that's an acceptable answer. Consider\n> \n> Oh, very good point.... |
[
{
"msg_contents": "Someone on IRC was confused by the contents of postgresql.conf:\n\t\n\t#ifdef USE_ASSERT_CHECKING\n\t#debug_assertions = true\n\t#endif\n\nI have to say I was confused myself. The #ifdef and #end are merely\ncomments, while appears like that syntax is supported by PostgreSQL. I\nthink we sh... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.