Re: [HACKERS] allowed user/db variables

2003-06-25 Thread Joe Conway
Christopher Kings-Lynne wrote: See my followup. Which bits of info would you like to see added that SHOW doesn't reveal? Unlike andreas, I'm not interested in the types and ranges of values, what I need to know is the GUC variables that the user is allowed to set, in particular what they can

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Christopher Kings-Lynne
Well, correct solution is to implement tablespaces on which objects like databases, tables and indexes can be put. I have started working on tablespaces (to the extent that I am capable!), based not on the rejected patch, but on Jim's eventual syntax proposal that was never developed. eg.

Re: [HACKERS] allowed user/db variables

2003-06-25 Thread Christopher Kings-Lynne
I was considering adding this and the stuff Andreas requested to pg_settings (but not SHOW ALL or SHOW x unless people feel it's important to kept them consistent with pg_settings). Were the Red Hat guys going to do this? pg_settings would be fine for phpPgAdmin. Chris

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Shridhar Daithankar
On 25 Jun 2003 at 14:55, Christopher Kings-Lynne wrote: Well, correct solution is to implement tablespaces on which objects like databases, tables and indexes can be put. I have started working on tablespaces (to the extent that I am capable!), based not on the rejected patch, but on

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Christopher Kings-Lynne
I have started working on tablespaces (to the extent that I am capable!), based not on the rejected patch, but on Jim's eventual syntax proposal that was never developed. Hmm... Remember feature freeze is 1st of July. So unless you send out a minimally working patch before that, it won't

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread scott.marlowe
On Tue, 24 Jun 2003, Dann Corbit wrote: -Original Message- From: The Hermit Hacker [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:10 PM To: Dann Corbit Cc: The Hermit Hacker; Jan Wieck; scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl; PostgreSQL-development

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Shridhar Daithankar
On 24 Jun 2003 at 14:48, Jonathan Bartlett wrote: I know the current method for specifying alternate drives for PG tables is by using symlinks. I had some ideas for simple ways to do this in PG code, but wanted to know if anyone was working on this right now. I'd hate to take the time to

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Shridhar Daithankar
On 25 Jun 2003 at 12:30, Shridhar Daithankar wrote: On 25 Jun 2003 at 14:55, Christopher Kings-Lynne wrote: Well, correct solution is to implement tablespaces on which objects like databases, tables and indexes can be put. I have started working on tablespaces (to the extent that I

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Kaare Rasmussen
That seems too vague for TODO. We might as well add Make PostgreSQL faster. :-) 'K, can you add that one too? :) How about * Remove all bugs from the source. Can you put that in TODO ? :-) -- Kaare Rasmussen--Linux, spil,--Tlf:3816 2582 Kaki Data

Re: [HACKERS] PHP/PgSQL *and* libpq ...

2003-06-25 Thread Robert Treat
Seems like we should also allow for a windows specific distribution of libpq as well. Robert Treat On Tuesday 24 June 2003 10:43 pm, Bruce Momjian wrote: Added to TODO: * Allow creation of a libpq-only tarball

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Jan Wieck
Kaare Rasmussen wrote: That seems too vague for TODO. We might as well add Make PostgreSQL faster. :-) 'K, can you add that one too? :) How about * Remove all bugs from the source. Can you put that in TODO ? :-) Change that into * Remove bugs from source code and get a patent on it. Should

Re: [HACKERS] allowed user/db variables

2003-06-25 Thread Andreas Pflug
Christopher Kings-Lynne wrote: I was considering adding this and the stuff Andreas requested to pg_settings (but not SHOW ALL or SHOW x unless people feel it's important to kept them consistent with pg_settings). Were the Red Hat guys going to do this? pg_settings would be fine for

Re: [HACKERS] PHP/PgSQL *and* libpq ...

2003-06-25 Thread Robert Treat
On Wed, 25 Jun 2003 08:59:41 -0300 (ADT), Marc G. Fournier wrote: On Wed, 25 Jun 2003, Robert Treat wrote: Seems like we should also allow for a windows specific distribution of libpq as well. I thought that the win32 stuff was being included as part of the base distribution? IF so,

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Andreas Pflug
Jan Wieck wrote: Change that into * Remove bugs from source code and get a patent on it. Should be a nobrainer (as in those guy's have no brains) considering that NetFlix even got a patent on DVD subscription rentals: http://slashdot.org/article.pl?sid=03/06/24/1458223mode=flattid=155tid=99

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Shridhar Daithankar
On 25 Jun 2003 at 14:50, Andreas Pflug wrote: Jan Wieck wrote: Change that into * Remove bugs from source code and get a patent on it. Should be a nobrainer (as in those guy's have no brains) considering that NetFlix even got a patent on DVD subscription rentals:

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Kaare Rasmussen
Change that into * Remove bugs from source code and get a patent on it. Should be a nobrainer (as in those guy's have no brains) considering that NetFlix even got a patent on DVD subscription rentals: And for all the nice royalty money*, think about what can be done to PostgreSQL. Maybe even

[HACKERS] timestamp bug?

2003-06-25 Thread Gavin Sherry
Shouldn't we be detecting problems with the following (haven't seen mention of it): template1=# insert into b values('1000-12-01 23:23:23'); INSERT 555183 1 template1=# select * from b; ERROR: Unable to format timestamp; internal coding error Tested on reasonably recent CVS. Mentioned on

Re: [HACKERS] allowed user/db variables

2003-06-25 Thread Tom Lane
I was considering adding this and the stuff Andreas requested to pg_settings (but not SHOW ALL or SHOW x unless people feel it's important to kept them consistent with pg_settings). Were the Red Hat guys going to do this? pg_settings would be fine for phpPgAdmin. Same for pgAdmin3. I

Re: [HACKERS] a problem with index and user define type

2003-06-25 Thread Tom Lane
Weiping He [EMAIL PROTECTED] writes: because the data type (UUID) is a struct, and the uuid_eq() function accept two pointer to the value of struct uuid, if make it IMMUTABLE, postgresql would think it should not try to run the function, but return the cached value instead when it get two same

Re: [HACKERS] [GENERAL] capturing and storing query statement with rules

2003-06-25 Thread Tom Lane
Joe Conway [EMAIL PROTECTED] writes: I was thinking something similar. This exact question has come up at least three times in the last three months. I doubt we'd want a special keyword like CURRENT_QUERY, but maybe current_query()? Not unless you want to promote a quick debugging hack, not

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Tom Lane
Bruce Momjian [EMAIL PROTECTED] writes: Patch applied. Thanks. Michael A Nachbaur wrote: Attached is a patch that provides *VERY* limited support for multiple slave servers. I haven't tested it very well, so use at your own risk (and I recommend against using it in production).

Re: [HACKERS] [GENERAL] capturing and storing query statement with

2003-06-25 Thread Joe Conway
Tom Lane wrote: Joe Conway [EMAIL PROTECTED] writes: I was thinking something similar. This exact question has come up at least three times in the last three months. I doubt we'd want a special keyword like CURRENT_QUERY, but maybe current_query()? Not unless you want to promote a quick

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Bruce Momjian
Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Patch applied. Thanks. Michael A Nachbaur wrote: Attached is a patch that provides *VERY* limited support for multiple slave servers. I haven't tested it very well, so use at your own risk (and I recommend against using it in

Re: [HACKERS] compile warnings

2003-06-25 Thread Tom Lane
Joe Conway [EMAIL PROTECTED] writes: Other than these 4 warnings, I get a clean compile on Red Hat 9 and 8.0 systems. I see a couple other warnings when building on HPUX, but all are in ecpg: gcc -O1 -Wall -Wmissing-prototypes -Wmissing-declarations -g -fpic

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Tom Lane
Christopher Kings-Lynne [EMAIL PROTECTED] writes: I have started working on tablespaces (to the extent that I am capable!), based not on the rejected patch, but on Jim's eventual syntax proposal that was never developed. Has anyone looked at the syntaxes used by other databases to control

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Alvaro Herrera
On Wed, Jun 25, 2003 at 11:11:35AM -0400, Bruce Momjian wrote: Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Patch applied. Thanks. Michael A Nachbaur wrote: Attached is a patch that provides *VERY* limited support for multiple slave servers. I haven't tested it very

[HACKERS] ECPG compile error

2003-06-25 Thread Rod Taylor
/usr/local/bin/gmake -C ecpglib all gmake[4]: Entering directory `/usr/home/rbt/work/postgresql/pgsqlwarning/src/interfaces/ecpg/ecpglib' gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -g -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -DPIC

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread johnnnnnn
On Wed, Jun 25, 2003 at 11:34:14AM -0400, Tom Lane wrote: Has anyone looked at the syntaxes used by other databases to control tablespaces (Oracle, DB2, etc)? I have no strong desire to slavishly follow Oracle, but it would be a shame to miss out on any good ideas. DB2: CREATE TABLESPACE

Re: [HACKERS] compile warnings

2003-06-25 Thread Michael Meskes
On Wed, Jun 25, 2003 at 11:22:58AM -0400, Tom Lane wrote: I see a couple other warnings when building on HPUX, but all are in ecpg: The problem is that I do not have access to HP-UX. All my development and testing is done on Linux right now. And on my Debian system I get no warning at all. gcc

Re: [HACKERS] ss_family in hba.c

2003-06-25 Thread Kurt Roeckx
On Tue, Jun 24, 2003 at 04:10:13PM -0400, Jason Tishler wrote: Bruce, On Tue, Jun 24, 2003 at 03:04:05PM -0400, Bruce Momjian wrote: Kurt Roeckx wrote: All that probably needed to change for cygwin was to no longer use sa_family_t in the getaddrinfo.c. But Jason reported he needed

Re: [HACKERS] ECPG compile error

2003-06-25 Thread Michael Meskes
On Wed, Jun 25, 2003 at 11:51:47AM -0400, Rod Taylor wrote: misc.c: In function `ECPGset_informix_null': misc.c:272: `LONG_LONG_MIN' undeclared (first use in this function) misc.c:272: (Each undeclared identifier is reported only once misc.c:272: for each function it appears in.) misc.c: In

Re: [HACKERS] ECPG compile error

2003-06-25 Thread Rod Taylor
Anyway, if you have and it appears you also have HAVE_LONG_LONG_INT_64 defined, which header file does provide the approprioate constants and how is it named? It seems INT_MIN etc. are there. /usr/include/machine/limits.h seems to have INT_MIN, etc. in them. -- Rod Taylor [EMAIL PROTECTED]

Re: [HACKERS] compile warnings

2003-06-25 Thread Tom Lane
Michael Meskes [EMAIL PROTECTED] writes: This is strange. According to my man page snprintf is declared in stdio.h which indeed is included. Where does HP-UX declare snprintf? It doesn't. Were you including our standard config headers, you'd get our standard workarounds for missing

Re: [HACKERS] ECPG compile error

2003-06-25 Thread Rod Taylor
Anyway, if you have and it appears you also have HAVE_LONG_LONG_INT_64 defined, which header file does provide the approprioate constants and how is it named? It seems INT_MIN etc. are there. Sorry, limits.h includes machine/limits.h. Which (after a fresh cvsup), I have your earlier fix. --

[HACKERS] still getting ecpg compile failures

2003-06-25 Thread Joe Conway
I saw a thread on this earlier, but I just cvsup'd (and `cvs up`, `make clean`, `make all`) and I'm getting: make[4]: Leaving directory `/opt/src/pgsql/src/interfaces/ecpg/include' make -C pgtypeslib all make[4]: Entering directory `/opt/src/pgsql/src/interfaces/ecpg/pgtypeslib' gcc -O2 -g -Wall

[HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Tom Lane
There are a number of things that need to be done in psql before feature freeze. Any comments on the following points? * We need a client-side autocommit-off implementation to substitute for the one removed from the server. I am inclined to create a new psql backslash command:

Re: [HACKERS] still getting ecpg compile failures

2003-06-25 Thread Michael Meskes
On Wed, Jun 25, 2003 at 10:36:09AM -0700, Joe Conway wrote: I saw a thread on this earlier, but I just cvsup'd (and `cvs up`, `make clean`, `make all`) and I'm getting: Not really surprising since I committed just one file but changed seven. I guess I better stop working on this for today.

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread AgentM
On Wednesday, June 25, 2003, at 12:10 PM, johnn wrote: On Wed, Jun 25, 2003 at 11:34:14AM -0400, Tom Lane wrote: Has anyone looked at the syntaxes used by other databases to control tablespaces (Oracle, DB2, etc)? I have no strong desire to slavishly follow Oracle, but it would be a shame to

[HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Tom Lane
I had originally planned to spend the next week editing all the elog() calls in the backend to convert them to ereport() format where helpful, add SQLSTATE values, and update wording to match the style guidelines that were agreed to awhile back. However, it looks like the same reasons that were

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Josh Berkus
Jan, There have been a good number of examples where the one who raised an issue isn't just of the format to implement it. So someone else jumped in and did it instead. I don't need to pick any particular samples, you know that it happened a few times. Sure. But in those cases, the

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Jeff
On Wed, 25 Jun 2003, Tom Lane wrote: Has anyone looked at the syntaxes used by other databases to control tablespaces (Oracle, DB2, etc)? I have no strong desire to slavishly follow Oracle, but it would be a shame to miss out on any good ideas. Informix is pretty bad. First, you use an

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Andrew Dunstan
DB2 looks good. I have horrid, horrid memories of wrestling with the Oracle extent madness. andrew AgentM wrote: On Wednesday, June 25, 2003, at 12:10 PM, johnn wrote: On Wed, Jun 25, 2003 at 11:34:14AM -0400, Tom Lane wrote: Has anyone looked at the syntaxes used by other databases to

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Tom Lane
Josh Berkus [EMAIL PROTECTED] writes: 3) Dann is proposing not just a feature but sweeping changes to the way our commmunity works, despite having been a member of this community for about 3 weeks total. In Dann's defense, I didn't think I heard him proposing that we get rid of our existing

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread johnnnnnn
On Wed, Jun 25, 2003 at 10:30:31AM -0500, Andrew Dunstan wrote: DB2 looks good. I have horrid, horrid memories of wrestling with the Oracle extent madness. I do think that it's worth providing additional access points to tablespaces, though. That is, it would make sense to me to allow CREATE

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread greg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since libpq now keeps track of transaction state, it would be a simple matter to add a prompt-string % construct to show something that indicates the state greg= SELECT 'I am idle'; greg=* SELECT 'I am in a transaction'; greg=! SELECT 'I am in

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread nolan
DB2 looks good. I have horrid, horrid memories of wrestling with the Oracle extent madness. I think Oracle's extents came from their fixed size data file legacy, in 9i the extent limits appear to be completely overridable and sometimes even ignored, such as the next extent size. I agree that

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Bruce Momjian
Tom Lane wrote: There are a number of things that need to be done in psql before feature freeze. Any comments on the following points? * We need a client-side autocommit-off implementation to substitute for the one removed from the server. I am inclined to create a new psql backslash

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Bruce Momjian
Good idea. This is similar to the pgindent run, though that usually happens just _before_ beta. --- Tom Lane wrote: I had originally planned to spend the next week editing all the elog() calls in the backend to convert

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Tom Lane
[EMAIL PROTECTED] writes: Not sure how important that really is, given that we don't recommend running psql against servers of different versions. We also do not check the version or throw a warning on a mismatched version, something I think it may be time to reevaluate. It would be easy

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Kevin Brown
Tom Lane wrote: Josh Berkus [EMAIL PROTECTED] writes: 3) Dann is proposing not just a feature but sweeping changes to the way our commmunity works, despite having been a member of this community for about 3 weeks total. In Dann's defense, I didn't think I heard him proposing that we

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Michael A Nachbaur
On Wednesday 25 June 2003 08:42 am, Alvaro Herrera wrote: On Wed, Jun 25, 2003 at 11:11:35AM -0400, Bruce Momjian wrote: Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Patch applied. Thanks. Michael A Nachbaur wrote: Attached is a patch that provides *VERY* limited

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Tom Lane
Bruce Momjian [EMAIL PROTECTED] writes: Good idea. This is similar to the pgindent run, though that usually happens just _before_ beta. Right. It still should; I'd recommend we do that after I finish the error message edits. I think at least one person had volunteered to help with the

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Bruce Momjian
Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Good idea. This is similar to the pgindent run, though that usually happens just _before_ beta. Right. It still should; I'd recommend we do that after I finish the error message edits. I think at least one person had volunteered

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Josh Berkus
Kevin, So...would it make sense to create a gborg project to which people who have written their own test suites can contribute whatever code and data they feel comfortable releasing? As a gborg project, it would be separate from the main PG distribution and would thus have no impact on the

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-06-25 Thread Andreas Pflug
johnn wrote: On Wed, Jun 25, 2003 at 10:30:31AM -0500, Andrew Dunstan wrote: DB2 looks good. I have horrid, horrid memories of wrestling with the Oracle extent madness. I do think that it's worth providing additional access points to tablespaces, though. That is, it would make sense

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Tom Lane
Bruce Momjian [EMAIL PROTECTED] writes: I think at least one person had volunteered to help with the editing; that might be a good thing if they're still willing. There's something upwards of 4000 elog calls to be looked at :-( Do we get error numbers with that? :-) That is the point ...

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Matthew T. O'Connor
From: Tom Lane [EMAIL PROTECTED] It would be easy (and essentially free, since libpq already gets the info) to add such a notice to psql startup. How do other people feel about it? How would you word the notice exactly? psql: server version is FOO, psql version is BAR, some things may not

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Paul Ramsey
Lots of hardcoded english... is i8n something which gets raised often, or is it lingue franca enough that people don't care? (Since all the messages are going to be looked at anyways...) Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: I think at least one person had volunteered to help

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Tom Lane
Paul Ramsey [EMAIL PROTECTED] writes: Lots of hardcoded english... What makes you think it's hardcoded? We've had internationalization support for awhile. (One of the results I'd like to accomplish in this pass is to reduce the number of junk messages that translators need to look at, by

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Paul Ramsey
Tom Lane wrote: Paul Ramsey [EMAIL PROTECTED] writes: Lots of hardcoded english... What makes you think it's hardcoded? We've had internationalization support for awhile. (One of the results I'd like to accomplish in this pass is to reduce the number of junk messages that translators need to

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Tom Lane
Paul Ramsey [EMAIL PROTECTED] writes: I am probably just misunderstanding something. See http://candle.pha.pa.us/main/writings/pgsql/sgml/nls.html regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread nolan
Is it too late to suggest that there be a way to have output displayed on screen AND output to a file? I've got my Oracle systems set up so that all sqlplus sessions do this, complete with using the process or session number as part of the output file name so each is unique. This gives me a

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread Dennis Björklund
On Wed, 25 Jun 2003, Paul Ramsey wrote: Ignorance on my part, probably. You mentioned elog() so I grepped for it and found lots of this stuff: elog(FATAL, data directory %s was not found, checkdir) elog(FATAL, could not read permissions of directory %s: %m, checkdir); I

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Tom Lane
[EMAIL PROTECTED] writes: Is it too late to suggest that there be a way to have output displayed on screen AND output to a file? tee perhaps? This is irrelevant to what I'm doing, in any case, and it's not an itch I feel personally. Work on it yourself if you want it ...

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Bruce Momjian
OK, I have backed out this patch. Hopefully we can get a more complete patch sometime. --- Michael A Nachbaur wrote: On Wednesday 25 June 2003 08:42 am, Alvaro Herrera wrote: On Wed, Jun 25, 2003 at 11:11:35AM -0400,

Re: [HACKERS] [GENERAL] capturing and storing query statement with

2003-06-25 Thread Bruce Momjian
Added to TODO: * Promote debug_query_string into a server-side function current_query() --- Joe Conway wrote: Tom Lane wrote: Joe Conway [EMAIL PROTECTED] writes: I was thinking something similar.

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Michael A Nachbaur
On Thursday 19 June 2003 07:36 pm, Michael A Nachbaur wrote: Attached is a patch that provides *VERY* limited support for multiple slave servers. I haven't tested it very well, so use at your own risk (and I recommend against using it in production). snip Okay, I just did some more testing,

[HACKERS] pg_dump, schemas and 7.4/7.3

2003-06-25 Thread Richard Huxton
I'd really like to be able to dump a single schema from 7.3 for a current project. Now I can write a script to run \dt and then pg_dump -t each table, but that's not going to help me with sequences etc. Of course, in 7.4 pg_dump will do exactly what I want, which seems to give me two options:

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Tom Lane
Bruce Momjian [EMAIL PROTECTED] writes: I think 'is_superuser' is more appropriate. Okay, fine. I forgot one other thing that is available from the recent libpq additions and needs to be exposed by psql: error message verbosity setting. What's there now is described in

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Alvaro Herrera
On Wed, Jun 25, 2003 at 02:47:52PM -0700, Michael A Nachbaur wrote: Anyway, it looks like it replicates the A table just fine, and the slaveb and slavec databases replicate just fine, but the SyncID was incremented by the SlaveA replication, and therefore b and c never get updated. I don't

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread The Hermit Hacker
On Wed, 25 Jun 2003, Bruce Momjian wrote: Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Patch applied. Thanks. Michael A Nachbaur wrote: Attached is a patch that provides *VERY* limited support for multiple slave servers. I haven't tested it very well, so use at your

Re: [HACKERS] Feature freeze and the great elog changeover

2003-06-25 Thread The Hermit Hacker
On Wed, 25 Jun 2003, Tom Lane wrote: I had originally planned to spend the next week editing all the elog() calls in the backend to convert them to ereport() format where helpful, add SQLSTATE values, and update wording to match the style guidelines that were agreed to awhile back. However,

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Arguile
On Wed, 2003-06-25 at 13:49, Tom Lane wrote: There are a number of things that need to be done in psql before feature freeze. Any comments on the following points? * We need a client-side autocommit-off implementation to substitute for the one removed from the server. I am inclined to

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread nolan
[EMAIL PROTECTED] writes: Is it too late to suggest that there be a way to have output displayed on screen AND output to a file? tee perhaps? Tee ALMOST does it. Try doing a \d while tee'ing the output, for example. I don't quite get everything back before it asks for the next input

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Tom Lane
Arguile [EMAIL PROTECTED] writes: On Wed, 2003-06-25 at 13:49, Tom Lane wrote: The first choice seems less verbose to me, but if anyone wants to make a case for the second, I'm open to it. Note that either of these could be put in ~/.psqlrc if someone wants autocommit off as their default.

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Kevin Brown
Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: I think 'is_superuser' is more appropriate. Okay, fine. I forgot one other thing that is available from the recent libpq additions and needs to be exposed by psql: error message verbosity setting. What's there now is described

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Kevin Brown
[EMAIL PROTECTED] wrote: [EMAIL PROTECTED] writes: Is it too late to suggest that there be a way to have output displayed on screen AND output to a file? tee perhaps? Tee ALMOST does it. Try doing a \d while tee'ing the output, for example. Try using script (start it from the

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Bruce Momjian
That was my feeling, but the author wasn't sure about the patch either, hence it was backed out. --- The Hermit Hacker wrote: On Wed, 25 Jun 2003, Bruce Momjian wrote: Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED]

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Tom Lane
Kevin Brown [EMAIL PROTECTED] writes: Tom Lane wrote: Also, I would like to provide the same set of options w.r.t. messages logged in the server log. Here there is an additional frammish that could be imagined, ie, more detail for more-serious errors. Any opinions about what it should look

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread The Hermit Hacker
On Wed, 25 Jun 2003, Shridhar Daithankar wrote: On 25 Jun 2003 at 14:50, Andreas Pflug wrote: Jan Wieck wrote: Change that into * Remove bugs from source code and get a patent on it. Should be a nobrainer (as in those guy's have no brains) considering that NetFlix even got a patent on

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread The Hermit Hacker
On Wed, 25 Jun 2003, Kevin Brown wrote: So...would it make sense to create a gborg project to which people who have written their own test suites can contribute whatever code and data they feel comfortable releasing? As a gborg project, it would be separate from the main PG distribution and

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Bruce Momjian
Tom Lane wrote: Kevin Brown [EMAIL PROTECTED] writes: Tom Lane wrote: Also, I would like to provide the same set of options w.r.t. messages logged in the server log. Here there is an additional frammish that could be imagined, ie, more detail for more-serious errors. Any opinions

[HACKERS] row description for domain in 7.4

2003-06-25 Thread John DeSoi
I created a domain with text as the data_type. When I get the row description message from the backend for a column using this domain, the type OID provided is for text (25) rather than the OID of the domain I created. I could have sworn I tested this in 7.3.x and the OID was for my domain.

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread Alvaro Herrera
On Wed, Jun 25, 2003 at 08:33:04PM -0300, The Hermit Hacker wrote: On Wed, 25 Jun 2003, Bruce Momjian wrote: Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Patch applied. Thanks. Michael A Nachbaur wrote: Attached is a patch that provides *VERY* limited support for

Re: [HACKERS] RServ patch to support multiple slaves (sorta)

2003-06-25 Thread The Hermit Hacker
On Wed, 25 Jun 2003, Alvaro Herrera wrote: Are you saying that it doesn't matter that it is made more broken? Sorry if I disagree... we should be trying to fix it, not the other way around. If it's so broken, why hasn't it received any improvement? Is there some problem with the underlying

Re: [HACKERS] Two weeks to feature freeze

2003-06-25 Thread Jan Wieck
Doesn't matter, this entire approach has a fundamental flaw. If the lungs are empty ... that means that the guy has an open thorax, the lungs are collapsed, and you'll probably have problems catching his attention to make your claim. Jan The Hermit Hacker wrote: On Wed, 25 Jun 2003, Shridhar

Re: [HACKERS] row description for domain in 7.4

2003-06-25 Thread Tom Lane
John DeSoi [EMAIL PROTECTED] writes: I created a domain with text as the data_type. When I get the row description message from the backend for a column using this domain, the type OID provided is for text (25) rather than the OID of the domain I created. I could have sworn I tested this in

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Tom Lane
Bruce Momjian [EMAIL PROTECTED] writes: Tom Lane wrote: One way I could imagine doing it is to split log_min_messages into three variables, along the lines of minimum message level to produce a TERSE report, minimum message level to produce a DEFAULT report, and minimum message level to

Re: [HACKERS] Updating psql for features of new FE/BE protocol

2003-06-25 Thread Larry Rosenman
--On Wednesday, June 25, 2003 22:58:39 -0400 Tom Lane [EMAIL PROTECTED] wrote: Bruce Momjian [EMAIL PROTECTED] writes: Tom Lane wrote: One way I could imagine doing it is to split log_min_messages into three variables, along the lines of minimum message level to produce a TERSE report, minimum

[HACKERS] recursive queries

2003-06-25 Thread Christopher Kings-Lynne
What's the chances of getting recursive queries in for 7.4? Chris ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Re: [HACKERS] recursive queries

2003-06-25 Thread Tom Lane
Christopher Kings-Lynne [EMAIL PROTECTED] writes: What's the chances of getting recursive queries in for 7.4? If you mean SQL99 WITH clauses, approximately zero ... unless you had an implementation you were planning to whip out of your hip pocket along about now. Andrew Overholt of Red Hat has

Re: [HACKERS] recursive queries

2003-06-25 Thread Christopher Kings-Lynne
If you mean SQL99 WITH clauses, approximately zero ... unless you had an implementation you were planning to whip out of your hip pocket along about now. Andrew Overholt of Red Hat has been working on this, but is certainly not going to make the Tuesday feature-freeze deadline. I was just

Re: [HACKERS] recursive queries

2003-06-25 Thread Tom Lane
Christopher Kings-Lynne [EMAIL PROTECTED] writes: Andrew Overholt of Red Hat has been working on this, but is certainly not going to make the Tuesday feature-freeze deadline. I was just wondering who was working on it and what the progress was...? It seemed to me that it must have been

Re: [HACKERS] [GENERAL] Many Pl/PgSQL parameters - AllocSetAlloc(128)?

2003-06-25 Thread Tom Lane
I said: It might work to get rid of the wild card case (line 1115), which'd reduce the number of outputs to product(nsupers+1). I doubt we really want any wild cards in there anymore. I've fixed the problem along the above lines. The patch against 7.3 branch is attached in case Reuven would