Re: [HACKERS] Open 7.1 items

On Wed, 24 Jan 2001, Bruce Momjian wrote: > Here are my open 7.1 items. Thanks for shrinking the list so far. > > --- > > FreeBSD locale bug AFAIK, Tom have fixed it, if this bug is about -funsigned-char > Reorder INSERT f

[HACKERS] Open 7.1 items

Here are my open 7.1 items. Thanks for shrinking the list so far. --- FreeBSD locale bug Reorder INSERT firing in rules Philip Warner UPDATE crash JDBC LargeObject short read return value missing SELECT cash_out(1) crashes

[HACKERS] TODO.deail

I have removed unused entries from TODO.detail. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania

Re: [HACKERS] Re: AW: Re: MySQL and BerkleyDB (fwd)

Added to TODO.detail/replication. > [ Charset ISO-8859-1 unsupported, converting... ] > > > I had thought that the pre-commit information could be stored in an > > > auxiliary table by the middleware program ; we would then have > > > to re-implement some sort of higher-level WAL (I thought of

Re: [HACKERS] Re: AW: Re: MySQL and BerkleyDB (fwd)

Added to TODO.detail/replication. [ Charset ISO-8859-1 unsupported, converting... ] > > I had thought that the pre-commit information could be stored in an > > auxiliary table by the middleware program ; we would then have > > to re-implement some sort of higher-level WAL (I thought of the lis

[HACKERS] 7.1 question

Magnus, is this done? > > Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes: > > > It is possible to make the above work (at least on MSVC). > > > The switch is /MD that needs to be used for both the psql.exe and > > > libpq.dll. This forces the use of Multithreaded DLL runtime > > libraries.

Re: [HACKERS] Bad REFERENCES behaviour

On Thu, 25 Jan 2001, Christopher Kings-Lynne wrote: > There seems to be a bug in the 'REFERENCES' statement. You can create > foreign key references to fields that do not exist, that then cause odd (ie. > hard to resolve) error messages. > > The operator error below (that should not be possible

[HACKERS] Bad REFERENCES behaviour

There seems to be a bug in the 'REFERENCES' statement. You can create foreign key references to fields that do not exist, that then cause odd (ie. hard to resolve) error messages. The operator error below (that should not be possible) is in creating a reference to a column that does not exist us

RE: [HACKERS] (one more time) Patches with vacuum fixes available .

> Did we decide against LAZY? Seems we have a number of people > concerned about vacuum downtime, and I can see this as a win > for them. If they don't specify LAZY, the code is not run. First sorry that I wasn't able to deal with vlazy earlier. Now I have one more open item for 7.1 - restoring

Re: [HACKERS] Re: postgresql.conf and postgres options

Defaults are listed as the assignment value, and of course, the are all commented out. > I think the list is great, show what can be configured rather than > guessing/digging to find it, where it belongs, in what order (if any), etc. > etc. etc. > The only addition I could think would be to la

Re: [HACKERS] FW: Postgresql on win32

I have added ./include/config.h.win32 to the RELEASE_CHANGES update list. > Magnus Hagander writes: > > > > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > > > We're losing this battle anyway. Look into > > > src/interfaces/libpq/libpq.rc. > > > > > > Ugh. Magnus, is there any reasonable way

RE: [HACKERS] Permissions on CHECKPOINT

> >Contrary to what the submitted documentation claims, there is no > >permission checking done on the CHECKPOINT command. > Should there be? > > Vadim seemed to indicate that he was going to make that restriction. > Perhaps I misunderstood. Yes, there should be permission checking - I'l

Re: [HACKERS] Re: [GENERAL] child table doesn't inherit PRIMARY KEY?

Thanks. Done. > Bruce Momjian wrote: > >> On Wed, 24 Jan 2001, Bruce Momjian wrote: > > >I smell TODO item. In fact, I now see a TODO item: > > > >* Unique index on base column not honored on inserts from inherited table > > INSERT INTO inherit_table (unique_index_col) VALUES (dup)

Re: [HACKERS] Re: unixODBC again :-(

Glad these items are being resolved. THis has sat around too long. Please keep discussing and come up with a good patch. We will help however we can. > [EMAIL PROTECTED] wrote: > > > Nick Gorham writes: > > > > > Well because the driver does not know where to get the config info > > > from,

Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Lookingfor . . . ]

Frank Joerdens writes: [randomly varying set of regression tests fail] > Running the tests on my Linux box gives no failed tests. Must I assume > that those failed tests indicate some issue that is is detrimental to > the proper functioning of the server on this Solaris installation? Do > you wa

Re: [HACKERS] This script will crash the connection

Tom Lane wrote: > "Steve Howe" <[EMAIL PROTECTED]> writes: > > create rule blah_update as > > on update to blah > >do > > notify TestEvent; > > > UPDATE blah SET n1=n1+1; -- Won't crash the connection > > UPDATE blah SET n1=2 WHERE var_field='aaa' AND n1=1 AND n2=2 AND arr_str IS > > NU

Re: [HACKERS] WAL documentation

Oliver Elphick writes: > Here's a patch to the wal.sgml text to take acocunt of Vadim's > explanations. I checked in your documentation plus some fixes at other places. Does somebody care to submit some new words to describe the fsync option (http://www.postgresql.org/devel-corner/docs/postgres

Re: [HACKERS] LEFT JOIN in pg_dumpall is a bug

Peter Eisentraut <[EMAIL PROTECTED]> writes: > I'm not sure whether this is actually an overall improvement. I'm tempted > to just coalesce(usename, {some default user}) instead. I thought about that to begin with, but figured you wouldn't like it ;-) regards, tom lane

Re: [HACKERS] WAL documentation

Here's a patch to the wal.sgml text to take acocunt of Vadim's explanations. *** wal.sgml.orig Wed Jan 24 21:55:56 2001 --- wal.sgml Wed Jan 24 22:08:44 2001 *** *** 149,154 --- 149,176 + + Database Recovery with WAL + + + After a checkpoint has been made and

Re: [HACKERS] Permissions on CHECKPOINT

Peter Eisentraut wrote: >Contrary to what the submitted documentation claims, there is no >permission checking done on the CHECKPOINT command. Should there be? Vadim seemed to indicate that he was going to make that restriction. Perhaps I misunderstood. If it's too late to make the change

Re: [HACKERS] Open 7.1 items

On Wed, 24 Jan 2001, Hannu Krosing wrote: > Bruce Momjian wrote: > > > > > You can't reasonably expect people to read all e-mail from last few > > > weeks > > > (probably a few thousands) and spot the same items as you. > > > > > > > May as well read the email rather than link to a web page. > >

[HACKERS] Re: postgresql.conf and postgres options

I think the list is great, show what can be configured rather than guessing/digging to find it, where it belongs, in what order (if any), etc. etc. etc. The only addition I could think would be to label (default value). Needless, I like it.. :) At 1/24/2001 01:03 PM, Bruce Momjian wrote: > >

Re: [HACKERS] function optimization ???

On 24 Jan 2001 at 12:14 (-0500), Tom Lane wrote: | Brent Verner <[EMAIL PROTECTED]> writes: | > calling it as: | > SELECT p.*, p.book_info.title FROM pricing p WHERE vista_ans='POD'; | > background and observation: | > the pricing table is fairly large, but only a small number meet | > "WHER

Re: [HACKERS] Open 7.1 items

> On Wed, 24 Jan 2001, Hannu Krosing wrote: > > > Bruce Momjian wrote: > > > > > > > You can't reasonably expect people to read all e-mail from last few > > > > weeks > > > > (probably a few thousands) and spot the same items as you. > > > > > > > > > May as well read the email rather than link t

[HACKERS] Permissions on CHECKPOINT

Contrary to what the submitted documentation claims, there is no permission checking done on the CHECKPOINT command. Should there be? Btw., is there any normal usage application of this command? This relates to the previous paragraph somewhat. -- Peter Eisentraut [EMAIL PROTECTED]

Re: [HACKERS] Re: [GENERAL] child table doesn't inherit PRIMARY KEY?

Bruce Momjian wrote: >> On Wed, 24 Jan 2001, Bruce Momjian wrote: >I smell TODO item. In fact, I now see a TODO item: > >* Unique index on base column not honored on inserts from inherited table > INSERT INTO inherit_table (unique_index_col) VALUES (dup) should fail > [inherit] >

Re: [HACKERS] LEFT JOIN in pg_dumpall is a bug

Tom Lane writes: > If you think depending on POSIX utilities is OK, then use cut. > I'd recommend sed, though. This has gotten pretty silly: TAB=' ' # tab here $PSQL -d template1 -At -F "$TAB" \ -c "SELECT datname, usename, pg_encoding_to_char(d.encoding), datistemplate, datpath, 'x' FROM

RE: [HACKERS] WAL documentation

> 1) In the 'WAL Parameters' section, paragraph 3 there is the following > sentence: "After a checkpoint has been made, any log segments written > before the redo record may be removed/archived..." What does the 'may' > refer mean? Does the database administrator need to go into the > directory

Re: [HACKERS] Open 7.1 items

Bruce Momjian wrote: > > > You can't reasonably expect people to read all e-mail from last few > > weeks > > (probably a few thousands) and spot the same items as you. > > > > > May as well read the email rather than link to a web page. > > > > Still it would be good to have a "TODO before 7.1 re

Re: [HACKERS] postgresql.conf and postgres options

Bruce Momjian wrote: > I have added all possible config options to postgresql.conf.sample. > I have attached the new version of the file. I think you will be amazed > at how GUC gives us such powerful control over PostgreSQL. Good. As a sysadmin I _like_ sample configs (which I usually rename

[HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

On Tue, Jan 23, 2001 at 11:57:52AM -0500, Tom Lane wrote: [ . . . ] > After you build PG and test it, send us a port report, and we'll add > Solaris 7 to the list of recently tested platforms. That's how it > works ... The installation by simply running configure, make, make install went complet

RE: [HACKERS] FW: Postgresql on win32

Magnus Hagander writes: > > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > > We're losing this battle anyway. Look into > > src/interfaces/libpq/libpq.rc. > > > > Ugh. Magnus, is there any reasonable way to generate that > > thing on the fly on Win32? > It's the same thing as with version.h -

Re: [HACKERS] Open 7.1 items

> You can't reasonably expect people to read all e-mail from last few > weeks > (probably a few thousands) and spot the same items as you. > > > May as well read the email rather than link to a web page. > > Still it would be good to have a "TODO before 7.1 relese" I send each article to the ap

Re: [HACKERS] Open 7.1 items

Bruce Momjian wrote: > > > On Wed, 24 Jan 2001, Bruce Momjian wrote: > > > > > > > It has to be done separately because you need to see the full content > > > > > and reply to each individually. Also, they go to different lists > > > > > sometimes. Pretty confusing. > > > > > > > > Could you po

Re: [HACKERS] Re: unixODBC again :-(

Nick Gorham writes: > Well because the driver does not know where to get the config info > from, Then the driver should be fixed to do that, with or without unixODBC. > libodbcinst.so in unixODBC provides SQLGetPrivateProfileString, > the location of user and system ini files are defined by thi

Re: [HACKERS] Strange.. solved

Actually, if you look in pg_trigger, is technically the constraint name and it should have a system generated constraint name which you probably can use drop trigger on. It looks like part of a FK constraint so I'm not sure how you got just 1/2 of it since dropping subject should have dropped i

[HACKERS] Re: [GENERAL] child table doesn't inherit PRIMARY KEY?

On Wed, 24 Jan 2001, Bruce Momjian wrote: > > OK, what do people want to do with this item? Add to TODO list? > > Seems making a separat unique constraint would be easy to do and be of > value to most users. The problem is that doing that will pretty much guarantee that we won't be doing fore

Re: [HACKERS] postgresql.conf and postgres options

> Bruce Momjian writes: > > > I have added all possible config options to postgresql.conf.sample. > > It was actually fully intentional that there was *no* list of all possible > config options in the sample file, because > > 1) Who's going to maintain this? > > 2) People should read the docum

RE: [HACKERS] WAL documentation

> The WAL logs auto-delete I think. At checkpoint time. Vadim

[HACKERS] Re: [GENERAL] child table doesn't inherit PRIMARY KEY?

> On Wed, 24 Jan 2001, Bruce Momjian wrote: > > > > > OK, what do people want to do with this item? Add to TODO list? > > > > Seems making a separat unique constraint would be easy to do and be of > > value to most users. > > The problem is that doing that will pretty much guarantee that we w

RE: [HACKERS] Re: AW: Re: MySQL and BerkleyDB (fwd)

> > 1. For 1st phase we'll place into log "prepared-to-commit" record > >and this phase will be accomplished after record is > >flushed on disk. > >At this point transaction may be committed at any time because of > >all its modifications are logged. But it still may be rolled bac

[HACKERS] PHP - Postgres large object functions

Adam, FYI, according to Rasmus Lerdorf, your patches have been committed. From the changelog: 2001-01-18 Derick Rethans <[EMAIL PROTECTED]> * ext/pgsql/pgsql.c ext/pgsql/php_pgsql.h: - Added the pg_lolseek function, which allows fo

Re: [HACKERS] LEFT JOIN in pg_dumpall is a bug

Peter Eisentraut <[EMAIL PROTECTED]> writes: >> Is there a more robust way of reading the data into the script? > Provided that 'cut' is portable, then this works for me: My old copy of Horton's _Portable C Software_ says that cut(1) is a SysV-ism adopted by POSIX. At that time (1990) it wasn't

Re: [HACKERS] postgresql.conf and postgres options

I have added all possible config options to postgresql.conf.sample. I have attached the new version of the file. I think you will be amazed at how GUC gives us such powerful control over PostgreSQL. Thanks, Peter. > Oliver Elphick writes: > > > 2. The following command line options to postgr

[HACKERS] Re: [INTERFACES] ODBC gives pq_recvbuf: unexpected EOF on client connection

Can someone research this? I heard JDBC has the same problem. > Cedar Cox <[EMAIL PROTECTED]> writes: > > I'm using ODBC/MS Access and every time my client shuts down > > I get the log message: > > pq_recvbuf: unexpected EOF on client connection > > Is there something I'm doing wrong here? >

[HACKERS] Re: [GENERAL] MySQL -> Postgres dump converter

Can someone look at both versions and merge the improvements into our version? Should be pretty easy. > > Can some PostgreSQL people comment on this? This person wrote a > > MySQL->PostgreSQL converter too. His version is at: > > http://ziet.zhitomir.ua/~fonin/code > > -- THIS VERSIO

Re: [HACKERS] (one more time) Patches with vacuum fixes available .

Bruce Momjian wrote: > > Did we decide against LAZY? Seems we have a number of people concerned > about vacuum downtime, and I can see this as a win for them. If they > don't specify LAZY, the code is not run. I see a number of possibilities: 1.) A tested 'feature patch' available for sepa

Re: [HACKERS] Re: unixODBC again :-(

Bruce Momjian writes: > > 1. Add options to use unixODBC in the configure.in file, the mainly consists of >finding the root of the unixODBC install prefix, and adding > > -I /unixODBC/path/include and -L /unixODBC/path/lib to the driver build --with-includes, --with-libraries > > 2. Change the

Re: [HACKERS] Libpq async issues

* Tom Lane <[EMAIL PROTECTED]> [010124 10:27] wrote: > Alfred Perlstein <[EMAIL PROTECTED]> writes: > > * Bruce Momjian <[EMAIL PROTECTED]> [010124 07:58] wrote: > >> I have added this email to TODO.detail and a mention in the TODO list. > > > The bug mentioned here is long gone, > > Au contrair

Re: [HACKERS] LEFT JOIN in pg_dumpall is a bug

Tom Lane writes: > > $PSQL -d template1 -At -F ' ' \ > > -c "SELECT datname, usename, pg_encoding_to_char(d.encoding), > > datistemplate, datpath FROM pg_database d LEFT JOIN pg_shadow u ON (datdba > > = usesysid) WHERE datallowconn;" | \ > > while read DATABASE DBOWNER ENCODING ISTEMPLATE DBPA

[HACKERS] Re: [PATCHES] Small patch to replace 'idle' by 'trans' if transactionisstill open

> Tom Lane writes: > > > Bruce Momjian <[EMAIL PROTECTED]> writes: > > > Any solid consensus on this? > > > > I'm for it (given a short status string --- "idle in tx" or "idle in trans" > > seem fine). Marc's for it. Who's against it? > > (I'm not.) If you're going to do "idle in trans" you m

Re: [HACKERS] (one more time) Patches with vacuum fixes available.

On Wed, 24 Jan 2001, Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Did we decide against LAZY? > > I thought the core consensus was that it was too risky to install > post-beta. On the other hand, we're installing some other pretty > major fixes. Do we want to re-open that dis

Re: [HACKERS] function optimization ???

Brent Verner <[EMAIL PROTECTED]> writes: > calling it as: > SELECT p.*, p.book_info.title FROM pricing p WHERE vista_ans='POD'; > background and observation: > the pricing table is fairly large, but only a small number meet > "WHERE vista_ans='POD'". I can select all where vista_ans='POD' >

[HACKERS] Re: [PATCHES] PgAccess schema-diagram cleanup

It got bounced to Constantin. I'm not sure if it's made it in, there. I'll ping him and see if he needs a new patch. Ross On Wed, Jan 24, 2001 at 08:49:13AM -0500, Bruce Momjian wrote: > > Ross, this looks very good. What happened to it? > > > Here's a patch to clean up some issues with the s

Re: [HACKERS] Libpq async issues

* Bruce Momjian <[EMAIL PROTECTED]> [010124 07:58] wrote: > > I have added this email to TODO.detail and a mention in the TODO list. The bug mentioned here is long gone, however the problem with issuing non-blocking COPY commands is still present (8k limit on buffer size). I hope to get to fix

Re: [HACKERS] BETWEEN patch

Thomas Swan <[EMAIL PROTECTED]> writes: > A patch to gram.y in src/backend/parser > Provides for the SQL99 expected behavior of > select * from foo where fo_num between 1 and 5 > yields the same result as > select * from foo where fo_num between 5 and 1 This is NOT correct under

Re: [HACKERS] Libpq async issues

Alfred Perlstein <[EMAIL PROTECTED]> writes: > * Bruce Momjian <[EMAIL PROTECTED]> [010124 07:58] wrote: >> I have added this email to TODO.detail and a mention in the TODO list. > The bug mentioned here is long gone, Au contraire, the misdesign is still there. The nonblock-mode code will *neve

RE: [HACKERS] FW: Postgresql on win32

> Peter Eisentraut <[EMAIL PROTECTED]> writes: > > We're losing this battle anyway. Look into > src/interfaces/libpq/libpq.rc. > > Ugh. Magnus, is there any reasonable way to generate that > thing on the fly on Win32? It's the same thing as with version.h - e.g. not really :-( It can be done,

Re: [HACKERS] Re: GreatBridge RPMs (was: Re: question)

Ypu can always use the source to build and install it instead of the RPM. At 07:18 PM 1/23/2001 +, Thomas Lockhart wrote: >> I'd hate to wait for the Mandrake specific RPM for every release. > >I've been building the Mandrake RPMs, and there is currently a small >problem in the build which I

Re: [HACKERS] Open 7.1 items

> > It has to be done separately because you need to see the full content > > and reply to each individually. Also, they go to different lists > > sometimes. Pretty confusing. > > Could you post a list of open issues where each has just a number, > heading > (optional) and link to an email in

Re: [HACKERS] PgAccess - small bug?

Has this been dealt with? > > > > > On Wed, 31 May 2000, Bruce Momjian wrote: > > > I assume this is fixed? > > Oh, it is really old letter from me. I total forget... > > Hmm, I haven't here last version of CVS, but pgaccess in my comp has this > bug still.. > > Bruce, thanks for ans

[HACKERS] Re: [PATCHES] RE: SSL Connections [doc PATCH]

> That would probably be good, yes :-) > > You shuold then change: > mv privkey.pem cert.pem.pw > openssl rsa -in cert.pem.pw -out cert.pem > > to > openssl rsa -in privkey.pem -out cert.pem > > (Sorry, don't have access to the SGML source now, so I can't give you a > patch) OK, the SGML diff

Re: [HACKERS] Open 7.1 items

> > > > They can not be easily summarized in one line. You really have to see > > > > the whole email to understand the issues. > > > > > > > > How do people want to do this? I can post them to hackers, or put them > > > > on my web site. I posted them to hackers during the past few days, but >

Re: [HACKERS] select within a fucntion

"Sinuhé Arroyo Gómez" wrote: > > The thing is that I´m not interested in wasting CPU nor my ystem is > oversized, and of course, "my friend", I willl use the results of the > select, because as a matter of fact it was a select .. into statement the > one I was trying, There was probably a syntax

Re: [HACKERS] Patches with vacuum fixes available for 7.0.x

On Wednesday 24 January 2001 20:37, Bruce Momjian wrote: > Here is another open item. What are we doing with LAZY vacuum? Sorry for inserting in the middle. I would like to say that when I tried LAZY vacuum on 7.0.3, I had a lockup on one of the table which disappeared after I did usual vacuum

Re: [HACKERS] Bug in FOREIGN KEY

We have to decide how to address this, perhaps with a clearer error message and a TODO item. > Bruce Momjian wrote: > > > Bruce Momjian writes: > > > > > > > ERROR: triggered data change violation on relation "primarytest2" > > > > > > We're getting this report about once every 48 hours, which

Re: [HACKERS] Open 7.1 items

On Wed, 24 Jan 2001, Bruce Momjian wrote: > > > It has to be done separately because you need to see the full content > > > and reply to each individually. Also, they go to different lists > > > sometimes. Pretty confusing. > > > > Could you post a list of open issues where each has just a numb

Re: [HACKERS] Open 7.1 items

Bruce Momjian wrote: > > > > > > They can not be easily summarized in one line. You really have to see > > > > > the whole email to understand the issues. > > > > > > > > > > How do people want to do this? I can post them to hackers, or put them > > > > > on my web site. I posted them to hacke

AW: [HACKERS] Postgresql on win32

> Thanks. Applied. > > [ Charset ISO-8859-1 unsupported, converting... ] > > Hello! > > > > Here is a patch to make the current snapshot compile on > Win32 (native, libpq > > and psql) again. Changes are: I thought the consensus was to do something other than that patch. As it looks, if noth

[HACKERS] RE: [PATCHES] RE: SSL Connections [doc PATCH]

Needs fixing - no. The current version *works*. The fix would remove one unnecessary step from it, but it still *works* in it's current state. Sorry about this - I've missed looking at it. //Magnus > -Original Message- > From: Bruce Momjian [mailto:[EMAIL PROTECTED]] > Sent: den 24 janu

[HACKERS] Cleanup time

I know it is a pain to have to deal with all these items, but we have to do this for every release. It helps to make our releases more complete because all open issues are resolved. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 8

Re: [HACKERS] This script will crash the connection

Bruce Momjian <[EMAIL PROTECTED]> writes: > Is there a TODO item here, Tom? Hopefully we can just decide what to do and do it. I'm waiting to hear Jan's opinion ... regards, tom lane

Re: [HACKERS] Open 7.1 items

Bruce Momjian wrote: > > I have trickled the emails as I reviewed them, asking for comments. It > was not one big email. ... > > > They can not be easily summarized in one line. You really have to see > > > the whole email to understand the issues. > > > > > > How do people want to do this?

[HACKERS] Re: [PATCHES] RE: SSL Connections [doc PATCH]

Again, is this something that needs fixing? Just a YES or NO is all I need. > It looks Ok, but it has one unnecessary step. There is no need to do the "mv > privkey.pem cert.pem.pw" if you just use "privkey.pem" in the following > openssl command (e.g. openssl rsa -in privkey.pem -out cert.pe

Re: [HACKERS] Open 7.1 items

> On Wed, 24 Jan 2001, Bruce Momjian wrote: > > > > > It has to be done separately because you need to see the full content > > > > and reply to each individually. Also, they go to different lists > > > > sometimes. Pretty confusing. > > > > > > Could you post a list of open issues where each h

[HACKERS] Re: [BUGS] select cash_out('2'); crashes backend on 7.0.2

Folks, I see we have many problems here: test=> select textout(2); pqReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally before or while processing the request. The connection

[HACKERS] Re: unixODBC again :-(

Folks, I need help on this. It would be nice to support unixODBC, but I don't understand the ramifications of these changes. > [EMAIL PROTECTED] wrote: > > > Nick, sorry this was never resolved. Do have any recollection of the > > issues involved? > > Hi Bruce, > > Yes I can tell you what I

[HACKERS] Re: [PATCHES] Small patch to replace 'idle' by 'trans' if transactionisstill open

Tom Lane writes: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Any solid consensus on this? > > I'm for it (given a short status string --- "idle in tx" or "idle in trans" > seem fine). Marc's for it. Who's against it? (I'm not.) If you're going to do "idle in trans" you might as well spell

Re: [HACKERS] (one more time) Patches with vacuum fixes available .

Did we decide against LAZY? Seems we have a number of people concerned about vacuum downtime, and I can see this as a win for them. If they don't specify LAZY, the code is not run. > The Hermit Hacker <[EMAIL PROTECTED]> writes: > > should be easily testable though, no? > > What makes you thi

[HACKERS] Re: [PATCHES] PgAccess schema-diagram cleanup

Ross, this looks very good. What happened to it? > Here's a patch to clean up some issues with the schema diagram > editor in pgaccess. This patch: > > * allows schema window to be resized up to full screen size > * autosizes window on schema open > * allows multiselect of ta

[HACKERS] Re: [GENERAL] User names

Seems like a bug that needs fixing. > "Glen and Rosanne Eustace" <[EMAIL PROTECTED]> writes: > > Is there a defined max length for postgreSQL user names ? > > If there is and it is 8, then createuser should enforce it. > > If the length is > 8 then pg_passwd needs fixing so that it doesn't > > t

Re: [HACKERS] Minor buglet in update...from (I think)

This still throws a strange error. Someone want to fix it? > > A minor nasty error I got when trying to improve the query used to disable > triggers: > > create table t1(f1 int4, f2 int4); > create table t2(f1 int4, f2 int4); > > insert into t1 values(1, 0); > insert into t1 values(2, 0); >

[HACKERS] Re: [GENERAL] child table doesn't inherit PRIMARY KEY?

OK, what do people want to do with this item? Add to TODO list? Seems making a separat unique constraint would be easy to do and be of value to most users. > > Probably, since I see it in near recent sources (and it affects > UNIQUE as well. As I remember it, the last discussion on this cou

[HACKERS] [JOB] pqsql hacker needed

We'd like to employ a Postgres hacker to speed development of enterprise features in Postgres. All code would be immediately contributed back to the community. We are not interested in proprietary extensions. We're a fun company located in Mountain View, CA, with all the usual benefits such as

[HACKERS] Re: [PATCHES] RE: SSL Connections [doc PATCH]

But shouldn't we remove it to make it clearer? > Needs fixing - no. The current version *works*. > The fix would remove one unnecessary step from it, but it still *works* in > it's current state. > > Sorry about this - I've missed looking at it. > > //Magnus > > > -Original Message- >

[HACKERS] function optimization ???

Hi, I've the following function: CREATE FUNCTION book_info(pricing) RETURNS catalog_general AS ' select * from catalog_general where star_isbn = $1.vista_isbn ' LANGUAGE 'sql'; calling it as: SELECT p.*, p.book_info.title FROM pricing p WHERE vista_ans='POD'; background

[HACKERS] Re: [GENERAL] rules on INSERT can't UPDATE new instance?

Comments on this? Seems INSERT should happen at the end. Is this a trivial change? > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Is the INSERT rule re-ordering mentioned a TODO item? > > Darn if I know. I threw the thought out for discussion, but didn't > see any comments. I'm not in a h

Re: [HACKERS] Patches with vacuum fixes available for 7.0.x

Here is another open item. What are we doing with LAZY vacuum? > We recently had a very satisfactory contract completed by > Vadim. > > Basically Vadim has been able to reduce the amount of time > taken by a vacuum from 10-15 minutes down to under 10 seconds. > > We've been running with the

Re: AW: [HACKERS] Postgresql on win32

OK, suggestions? [ Charset ISO-8859-1 unsupported, converting... ] > > > Thanks. Applied. > > > > [ Charset ISO-8859-1 unsupported, converting... ] > > > Hello! > > > > > > Here is a patch to make the current snapshot compile on > > Win32 (native, libpq > > > and psql) again. Changes are:

Re: [HACKERS] WAL fsync scheduling

Added to TODO.detail and TODO list. > [ Charset ISO-8859-1 unsupported, converting... ] > > > There are two parts to transaction commit. The first is writing all > > > dirty buffers or log changes to the kernel, and second is fsync of the > > > > Backend doesn't write any dirty

Re: [HACKERS] Inline Comments for pg_dump

Do we handle COMMENT properly in pg_dump now already? [ Charset ISO-8859-1 unsupported, converting... ] > I've very roughly (first time I've tried anything but hello world c) hacked up >inline comments. > > pg_dump -I > > Exports the comments generated through COMMENT ON in an appropriate ma

[HACKERS] Libpq async issues

I have added this email to TODO.detail and a mention in the TODO list. > >> Um, I didn't have any trouble at all reproducing Patrick's complaint. > >> pg_dump any moderately large table (I used tenk1 from the regress > >> database) and try to load the script with psql. Kaboom. > > > This is af

[HACKERS] BETWEEN patch

A patch to gram.y in src/backend/parser Provides for the SQL99 expected behavior of select * from foo where fo_num between 1 and 5 yields the same result as select * from foo where fo_num between 5 and 1 Granted this is brute force and not very elegant, however it does provide

[HACKERS] RE: [PATCHES] RE: SSL Connections [doc PATCH]

That would probably be good, yes :-) You shuold then change: mv privkey.pem cert.pem.pw openssl rsa -in cert.pem.pw -out cert.pem to openssl rsa -in privkey.pem -out cert.pem (Sorry, don't have access to the SGML source now, so I can't give you a patch) //Magnus > -Original Message- >

Re: [HACKERS] PgAccess - small bug?

[ Charset ISO-8859-1 unsupported, converting... ] > - Original Message - > From: "Bruce Momjian" <[EMAIL PROTECTED]> > To: "Karel Zak" <[EMAIL PROTECTED]> > Cc: "pgsql-hackers" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Wednesday, January 24, 2001 3:41 PM > Subject: Re: [HACKERS] Pg

Re: [HACKERS] (one more time) Patches with vacuum fixes available .

Bruce Momjian <[EMAIL PROTECTED]> writes: > Did we decide against LAZY? I thought the core consensus was that it was too risky to install post-beta. On the other hand, we're installing some other pretty major fixes. Do we want to re-open that discussion? regards, tom la

Re: AW: [HACKERS] like and optimization

On Mon, Jan 22, 2001 at 03:09:03PM -0800, Nathan Myers wrote: ... > Posix systems include a set of commands for dumping locales in a standard > format, and building from them. Instead of shipping locales and code to > operate on them, one might include a script to run these tools (where > the

Re: AW: [HACKERS] like and optimization

On Mon, Jan 22, 2001 at 05:46:09PM -0500, Tom Lane wrote: ... > Are there any BSD-license locale and/or timezone libraries that we might > assimilate in this way? We could use an LGPL'd library if there is no > other alternative, but I'd just as soon not open up the license issue. The "Citrus P

Re: [HACKERS] select within a fucntion

The thing is that I´m not interested in wasting CPU nor my ystem is oversized, and of course, "my friend", I willl use the results of the select, because as a matter of fact it was a select .. into statement the one I was trying, but to make it easier to understand (I now see you were so smart tha

[HACKERS] Re: PostgreSQL on WinME?

Hi there, I would like to inquire of any support for WinME to run PostgreSQL. Should anyone knows how, I would be grateful to ask for advice. I need to run PostgreSQL on my WinME box. -- Manny C. Cabido =

  1   2   >