IIRC the message at the end of install used to echo out the startup
command (pg_ctl or postmaster), but now it gives some nice information
on how to get help. Should the startup message be put back in? Seems
like it is the most likely thing someone who just installed would want
to know.
Robert
On Tue, 12 Aug 2003, Christopher Kings-Lynne wrote:
rbt=3D# ALTER USER rbt SET CONSTRAINTS ALL DEFERRED;
ERROR: syntax error at or near ALL at character 32
rbt=3D# ALTER USER rbt SET CONSTRAINTS =3D DEFERRED;
ERROR: constraints is not a recognized option
SET CONSTRAINTS ALL
On Tue, 12 Aug 2003, Tom Lane wrote:
I have just finished running some experiments that compared a series of
INSERTs issued via PQexec() versus preparing an INSERT command and then
issuing new-FE-protocol Bind and Execute commands against the prepared
statement. With a test case like the
On Sat, Aug 09, 2003 at 07:06:58PM -0400, Andrew Dunstan wrote:
I am seeing this (RH8 - cvs tip):
2003-08-09 18:55:14 [6680] LOG: failed to create socket: Address family
not supported by protocol
Probably harmless - presumably refers to IPv6 not running, but annoying
nevertheless,
Your pg_dump's actually invoke the pager? Are you manually starting
psql, then doing \i dumpfile? Why would you do that rather than psql
template1 dumpfile?
Because I'm a dork :-).
Seriously, sometimes it's useful.
The most useful reason (and I wish you could turn it on with psql
The below function works in 7.3 (returns nothing, but no errors).
rbttest=# begin;
BEGIN
rbttest=# create or replace function service.test(integer)
rbttest-# returns setof service.service
rbttest-# as '
rbttest'# declare
rbttest'# v_service service.service%rowtype;
rbttest'#
rbttest'# begin
Bruce Momjian [EMAIL PROTECTED] writes:
/* Limit non-superuser changes */
if (record-context == PGC_USERLIMIT
source PGC_S_UNPRIVILEGED
newval conf-session_val
^^^
I had in mind
Rahul_Iyer [EMAIL PROTECTED] writes:
im on a project using Postgres. The project involves, at times, upto
5,000,000 inserts. I was checking the performance of Postgres for 5M inserts
into a 2 column table (one col=integer, 2nd col=character). I used the
Prepare... and execute method, so i
On Wed, Aug 13, 2003 at 06:05:46PM -0400, Bruce Momjian wrote:
I tried adding this line:
record-session_source PGC_S_UNPRIVILEGED
and it does allow you to set the variable to false if you have set it to
true in your session, but it also allows you to set it to false if it is
set
On Tuesday 05 August 2003 03:15, Shridhar Daithankar wrote:
I am willing to build 7.4beta binaries on slackware and upload them
someplace. This is just to add to binary packages readily available.
Can anybody tell me what flags etc. are to be used. I have a slackware 9.0
installation with
Yes, this is the right fix. I never suspected wsock32 would exist on a
non-MS WIn machine.
---
Tom Lane wrote:
elein [EMAIL PROTECTED] writes:
It sounds like Joe's guess on this was right.
I've committed this fix in
Andreas Pflug wrote:
But PostgreSQL may be better than Oracle, don't you think? In the named
document,
snip
MSSQL2000 still doesn't have row level triggers, and I doubt that 2003 has.
Right, so as you've pointed out, Postgres trigger implementation is at
least in some ways more flexible than
The situation seems to be a bug that this patch would address. It seems to
me that when a username is considered unsafe due to containing double
quotes, the double quotes should be escaped (and the backslashes)!
Does this look alright?
Chris
Index: src/backend/utils/adt/acl.c
Jenny - [EMAIL PROTECTED] writes:
how do we check whether blockId and tupleId of LOCK.tag are valid or
invalid?
Look at how LockRelation and LockPage (in
src/backend/storage/lmgr/lmgr.c) set up the tags --- it might be clearer
then.
regards, tom lane
Bruce Momjian [EMAIL PROTECTED] writes:
Seems we have a problem with pooled connections and WITH HOLD cursors.
We have code to reset transaction state and variables via RESET ALL, but
how do we remove WITH HOLD cursors when we pass a connection to a new
client?
Prepared statements would be
I have updated ecpg/test/test_thread.pgc to do an automated thread test.
First, update to current CVS. Then, run configure with
--enable-thread-safety, compile/install, then go to ecpg/test, and do a
'gmake', then run 'test_thread dbname'. It should return success or
failure.
I hope this
Hi all,
I am willing to build 7.4beta binaries on slackware and upload them someplace.
This is just to add to binary packages readily available.
Can anybody tell me what flags etc. are to be used. I have a slackware 9.0
installation with most of the developer tools I believe. I can give it a
Joe,
This isn't isolated to just PL/pgSQL, just like the ability to create
and call functions isn't. Support for PROCEDUREs in the backend is a
prerequisite to being able to use PL/pgSQL to create procedures. It is
necessary but not sufficient.
Similarly, if we want to support IN/OUT or
On Tue, 5 Aug 2003, Tom Lane wrote:
The Hermit Hacker [EMAIL PROTECTED] writes:
Please test and let me know if there are any problems ...
The .gz tarball matches what I have here. Didn't check the .bz2 one.
All the .bz2 one is is 'gunzip *.gz;bzip2 *.tar', so should be good :)
On Wed, Aug 06, 2003 at 12:05:47 -0700,
The Pennant Shop [EMAIL PROTECTED] wrote:
Hi ,
I have a table:
item location
aaa 10
aaa 20
bbb 10
bbb 10
ccc 10
ccc 20
I need to select distinct items where locations are
the same. So result set should look like:
item loation
Andreas Pflug wrote:
YATS (yet another TODO suggestion):
provide an official and reliable way to temporarily enable/disable triggers.
ALTER TABLE xxx ENABLE/DISABLE TRIGGER ALL/trgName
We still have that nasty not presently checked everywhere it should be
comment in the doc for
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I was just testing the threaded ecpg, and ran some performance tests.
Without using threads, I am seeing 100,000 inserts of a single word into
a simple table take 12 seconds:
CREATE TABLE test_thread(message TEXT);
giving me
Tom Lane writes:
One of the reasons for not doing conversion in binary mode is to have an
escape hatch for unconvertible characters, eg for dump purposes.
That functionality is already provided by setting the client encoding to
SQL_ASCII.
--
Peter Eisentraut [EMAIL PROTECTED]
elein [EMAIL PROTECTED] writes:
Yes, I actually have a libwsock32 because my
system has wine on it. Wine is a windows
emulator.
And they drop windows-only libraries into /usr/lib? Yech.
Anyway, I can't see a need to include libwsock32 on non-win32 platforms.
Will modify configure.
On Fri, 8 Aug 2003, Tom Lane wrote:
Stephan Szabo [EMAIL PROTECTED] writes:
I got the same thing as Gaetano on my just prior to beta1 system.
Well, we couldn't have fixed it since beta1 --- there's been no changes
anywhere near SPI. I'm thinking it must be platform-dependent. What
are
--On Saturday, August 09, 2003 12:31:06 -0500 Larry Rosenman
[EMAIL PROTECTED] wrote:
Another issue: plpgsql.so needs the elog() function, but it's not
exported...
actually, this is because of a hardcoded path in my old db, it was picking
up the 7.3.4 plpgsql.so.
LER
--
Larry Rosenman
RH8, cvs tip. I get this:
[EMAIL PROTECTED] src]$ make man.tar.gz
D2MDIR=/usr/share/sgml/docbook/utils-0.6.11/helpers
make -C sgml man
make[1]: Entering directory `/home/andrew/foo/pgsql/doc/src/sgml'
{ \
echo !entity version \7.4beta1\; \
echo !entity majorversion \`expr 7.4beta1 :
Bruce Momjian [EMAIL PROTECTED] writes:
On a philosophical note, I usually don't add core folks to release items
_with_ other folks because we want to encourage non-core contributors,
and because there is already the assumption that core is involved in
many patches.
I agree with this. For
Yes, I actually have a libwsock32 because my
system has wine on it. Wine is a windows
emulator.
So the assumption that any system with that
file is a windows system will break on
systems with windows emulators.
It sounds like Joe's guess on this was right.
--elein
On Mon, Aug 11, 2003 at
I forgot to say to do a:
select bar()
at the end!
Gaetano
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Mon, 11 Aug 2003, Peter Eisentraut wrote:
Alexey Mahotkin writes:
AFAIK, currently the codepoints are sorted in their numerical order. I've
searched the source code and could not find the actual place where this is
done. I've seen executor/nodeSort.c and utils/tuplesort.c. AFAIU,
I've just sent off patches to pgsql-patches to:
1. Slight clarification to the COPY BINARY format docs
2. A contrib/binarycopy module which wraps-up the detail of creating a
file which can be used as input to COPY BINARY. User can create either
7.1 or 7.4 format files using the same API, without
'k, removed and trying build again ...
On Tue, 5 Aug 2003, Tom Lane wrote:
The Hermit Hacker [EMAIL PROTECTED] writes:
GNUMakefile.in:
opt_files := \
src/tools src/corba src/data src/tutorial \
Ah.
I take it then, that src/data shoudl be removed from there too?
Yep. Sorry
On Sun, 10 Aug 2003, Andrew Dunstan wrote:
Time to install gcc? I believe it's doable for UW.
Yeah, SCO even supplies same. I do get fast turn around, I know
the compiler guys. They are already on the case, and fixing these
2.
I haven't touched UW in about 10 years, but I see not much has
Andreas Pflug [EMAIL PROTECTED] writes:
Consider this:
Table with one column that is maintained by a trigger for this rule:
- Only one row in a group of rows may have a foo-value of true, all
others must be false.
- If foo=true is inserted/updated, other members of that data group must
be
Hey again,
Received this error:
Aug 6 16:24:55 thunder postgres[7835]: [11-1] ERROR: variable not
found in subplan target lists
during this query:
$dbh-do( qq/
DELETE FROM temp_obs_v
WHERE file_id IN
(SELECT file_id
FROM temp_obs_v NATURAL JOIN files
WHERE group_id =
Doh - forget I even asked that! Setting default to something involving
current_time easily gives a variable default...
Chris
- Original Message -
From: Christopher Kings-Lynne [EMAIL PROTECTED]
To: Hackers [EMAIL PROTECTED]
Sent: Tuesday, August 05, 2003 9:46 AM
Subject: [HACKERS]
Neil Conway [EMAIL PROTECTED] writes:
Since the culprit functions all seem related (I believe they're
all generated by src/backend/utils/mb/conversion_procs), I'd
imagine this should be pretty easy to fix.
They should all be marked STRICT. Not sure how this got missed before;
thanks for
On Fri, 2003-08-08 at 11:55, Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
the following code was working properly under Postgres 7.3.X
I'm now running my regression test with Postgres 7.4beta1 and I'm
having the error in subj.
I tried this and got
regression=# select
Which suggests to me that line 3964 in
./src/backend/utils/adt/selfuncs.c isn't right for multi-column
indexes, esp for indexes that are clustered. I don't know how to
address this though... Tom, any hints?
Yes, we knew that already. Oliver had suggested simply dropping the
division
I have moved simple_prompt()/sprompt.c into /port. It was used by psql,
pg_dump, and scripts, and had already gotten out of sync with a recent
Win32 password patch.
If a file is needed by three non-backend directories, /port seems to be
the proper place for it.
--
Bruce Momjian
Bruce Momjian [EMAIL PROTECTED] writes:
It just seemed complex to figure out which operators needed parens and
which didn't.
The fact that the first attempt was wrong doesn't improve my faith in
that code one bit ;-). I don't want pg_dump invoking it, even as an
option. Someone will get
gnore
---(end of broadcast)---
TIP 8: explain analyze is your friend
What is the index temp_obs_i_obs_id_index on, exactly? Is it a serial
column or some such?
Yup:
Okay, that explains it then. In a serial column's index, essentially
all splits will be on the rightmost page of the tree. This means that
when bt_split tries to get a new free page, it will
Another interesting idea, if we do a single log variable with parameters
separated by commas, is to allow some syntax where you could specify the
delimiter between fields, so it could be:
log_line: |, dbname, username
or
log_line:, dbname, username
From: Tom Lane [EMAIL PROTECTED]
To: Jenny - [EMAIL PROTECTED]
Subject: Re: [HACKERS] this is in plain text (row level locks) Date: Sat,
02 Aug 2003 23:28:30 -0400
if row-level locks are not recorded in proclock or any other shared
memory
datastructuers, then why does lockmode (array or
hi, does anyone know what session level locks mean in postgresql..i've heard
of table-level locks and row level locks but not session level
thanks
Jenny
_
The new MSN 8: advanced junk mail protection and 2 months FREE*
Bruce Momjian wrote:
I am marking the completed TODO items. Are these done?
Can we mark this one complete?
* Allow easy display of usernames in a group
regression=# SELECT g.grosysid, g.groname, s.usesysid, s.usename FROM
pg_shadow s, pg_group g WHERE s.usesysid = any (g.grolist);
grosysid |
Stephan Szabo [EMAIL PROTECTED] writes:
I got the same thing as Gaetano on my just prior to beta1 system.
Well, we couldn't have fixed it since beta1 --- there's been no changes
anywhere near SPI. I'm thinking it must be platform-dependent. What
are you guys using, exactly?
On 7 Aug 2003 at 19:54, Bruce Momjian wrote:
Man, I can't do anything right; should be:
one INSERT per transaction, fsync true 934
one INSERT per transaction, fsync false 1818
INSERTs all in one transaction, fsync true 4166
Just curiousity, what will
The docs (new and old) explicitly state you can do this; see for example
http://www.postgresql.org/docs/7.3/static/sql-dropuser.html
But ISTM that in such a case the user's objects should possibly be
reassigned to the database owner (who can't be dropped), in kinda the
same way that a *nix
On Tue, 12 Aug 2003, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
but pgstat_initstats() caught my eye. This gets called about 6 times per
insert (I did 10 inserts) and the major cost appears to relate to the
linear pgStatTabstatMessages. The comparative performance of
I think I have a catalog corruption (self inflicted I'm sure). A dump /
reload of the database corrects the issue here as well.
On Thu, 2003-08-14 at 08:33, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
The below function works in 7.3 (returns nothing, but no errors).
rbttest=3D#
Andrew Dunstan [EMAIL PROTECTED] writes:
The dbname patch is now done. If nobody objects to the format
([db:yourdbname]) I'll submit it - I did it that way to make it fairly
easy to split a log file based on it, although you would have to be
careful with multiline log entries such as query
Nope, but Tom is actively on my box :-)
LER
--On Thursday, August 07, 2003 19:35:05 +0200 [EMAIL PROTECTED] wrote:
Did you find a work around?
On Thu, 7 Aug 2003, Larry Rosenman wrote:
Date: Thu, 07 Aug 2003 12:28:52 -0500
From: Larry Rosenman [EMAIL PROTECTED]
To: [EMAIL PROTECTED],
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Seems we have a problem with pooled connections and WITH HOLD cursors.
We have code to reset transaction state and variables via RESET ALL, but
how do we remove WITH HOLD
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
But should the CREATE DOMAIN manual page refer to DROP TYPE? Should DROP
DOMAIN be able to drop a type?
shrug Don't care much about either of those; the current state of
affairs is fine with me.
What happens in the
Do a CVS update and you should be fine. I modified that about 20 minutes ago.
---
Bruno Wolff III wrote:
I get the error message below when trying to make inside of the contrib
subdirectory. It was happening last night as
hi
whenever i call an execute on a prepared statement, i get the return value
of PQcmdTuples() as NULL even if the query did modify tuples...
how can i get the number of affected tuples?
thanx in adv.
rahul
---(end of broadcast)---
TIP 1: subscribe
Bruce Momjian [EMAIL PROTECTED] writes:
* Use index to restrict rows returned by multi-key index when used with
non-consecutive keys or OR clauses, so fewer heap accesses
Not sure what this means.
This is a Vadim idea. The idea was that if you had a multi-key index on
col1,col2,col3, and
Josh Berkus wrote:
Bruce,
o Allow array declarations and other data types in PL/PgSQL DECLARE
o Allow PL/PgSQL to support array element assignment
AFAIK, these two are not done, but they are redundant. Either one requires
the implementation of the other.
OK.
On Tuesday 05 August 2003 08:14, Andrew Dunstan wrote:
Will check later today.
When you do, let me know, so that I can post them.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
---(end of broadcast)---
TIP
Seems pg_dump dumps funcions with a space between the function name and
opening paren. It looks strange:
SELECT pg_catalog.setval ('test_x_seq', 1, false);
This patch removes the space:
SELECT pg_catalog.setval('test_x_seq', 1, false);
I didn't even realize the space worked,
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Cool. It's just down to this now:
gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -Wno-error
-I./../include -I. -I../../../../src/include -DMAJOR_VERSION=3 -DMINOR_VE
RSION=0 -DPATCHLEVEL=0
On Thu, Aug 07, 2003 at 05:20:58PM +0200, [EMAIL PROTECTED] wrote:
Hi Tom,
I have NI_NUMERICHOST defined in netdb.h
That's for getnameinfo(). getnameinfo() is older than
getaddrinfo() ...
If you have that, I assume you have AI_NUMERICHOST in the same
file too ... ?
Kurt
According to that logic, a view is a table, but we still require DROP
VIEW
to drop a view.
No, a view is not a table. Try putting an index or trigger on it.
It seems to me to be more correct that we make DROP TYPE not work on
domains. I refer to the principle of least surprise... People
Bruno Wolff III wrote:
array_iterator.c:30: utils/fmgroids.h: No such file or directory
make: *** [array_iterator.o] Error 1
I must have caught something in the middle of an update. I grabbed a fresh
copy a little while ago and now it builds properly.
I believe utils/fmgroids.h is a derived file.
Christopher Kings-Lynne wrote:
I assume we don't want them always quoted.
Problem with that is that someone has to move the to-quote-or-not function
from pg_dump into psql...
Attached is a psql/Makefile patch that makes fmtId() available to psql C
code.
I tried a test and it seemed to
Tom,
I'm prepared to be guided by concensus, though.
I'm not dead set on it either, just wanted to raise a flag. Who else
has an opinion?
From my perspective, we could really use a delimiter between the fields of
log output which is unlikely to appear within those fields instead of
Josh Berkus wrote:
o Allow array declarations and other data types in PL/PgSQL DECLARE
o Allow PL/PgSQL to support array element assignment
AFAIK, these two are not done, but they are redundant. Either one requires
the implementation of the other.
They are done (at least the array
On Fri, Aug 08, 2003 at 03:32:05PM +0530, Rahul_Iyer wrote:
im currently working on a project that requires batch operations - eg. Batch
insert/update etc. The database im using is PostgreSQL. However, i cannot
find any documentation for batch opeartions on PostgreSQL. Does anyone know
how to
To support some of the logging changes I'm working on, I propose to add
the following members to struct Port, unless anyone objects - these are
all calculated in postmaster/postmaster.c:
struct tm session_start;
char * remote_host;
char * remote_port;
Question: In setting these is it better
Tom Lane writes:
The advantage here is that the sysid assigned to the user would remain
present in pg_shadow and couldn't accidentally be assigned to a new
user. This would prevent the problem of new users inheriting
permissions and even object ownership from deleted users due to chance
Rod Taylor [EMAIL PROTECTED] writes:
rbt=3D# ALTER USER rbt SET CONSTRAINTS ALL DEFERRED;
ERROR: syntax error at or near ALL at character 32
rbt=3D# ALTER USER rbt SET CONSTRAINTS =3D DEFERRED;
ERROR: constraints is not a recognized option
SET CONSTRAINTS ALL DEFERRED is a SQL-spec-mandated
On Tue, 12 Aug 2003, Tom Lane wrote:
This leaves us with a bit of a problem, though, because there isn't any
libpq API that allows access to this speedup. I put in a routine to
support Parse/Bind/Execute so that people could use out-of-line
parameters for safety reasons --- but there's no
Hello everybody,
how far have you got with statement-level triggers development?
Regards,
Claudio.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Retired? May be is better: Hall of fame.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I appear to have a hang on my system (40 minutes so far, it's now
17:40). The code is from CVS updated 8/6 if I remember correctly.
The machine is idle, with a vacuum waiting and an INSERT doing nothing.
The vacuum is being generated via pg_autovacuum.
The output from the perl script leading
could be \dn for describe namespace for ei : \dn pg_catalog,
or only \dn to list all namespaces
?
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Tom Lane kirjutas R, 08.08.2003 kell 16:56:
Bruce Momjian [EMAIL PROTECTED] writes:
o Add optional textual message to NOTIFY
Not done, but there is room in the FE/BE protocol now for something like
this.
Were there any other changes to NOTIFY - there was talk about making
NOTIFY
Andreas Pflug [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
OTOH I'm not sure how much harm this causes, other than aesthetic.
Dropping a user could merely set a dropped flag to disable login, and
some VACUUM action could cleanup databases.
Not sure I care for the vacuum part of that,
Mendola Gaetano [EMAIL PROTECTED] writes:
Again the error:
kalman=# select bar();
ERROR: consistency check on SPI tuple count failed
CONTEXT: PL/pgSQL function bar line 5 at for over select rows
kalman=# select bar();
ERROR: consistency check on SPI tuple count failed
CONTEXT: PL/pgSQL
Christopher Kings-Lynne kirjutas N, 07.08.2003 kell 04:33:
My other question is we play around with bytea fields to escape nulls and
chars 32 and stuff so that when someone browses the table, they get
'\000unknown\000...', etc.
actually bytea *stores* char(0), you get \000 or \x0 or @ or
hi, Tom and Momjian
Is PITR also delayed to 7.5?Right?
3x
Jinqiang Han
[EMAIL PROTECTED]
2003-08-05
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
I received the following note from the original author of dbf2pg:
Date: Tue, 05 Aug 2003 18:43:22 +0400
From: Maarten Boekhold [EMAIL PROTECTED]
Subject: Re: status of dbf2pg
To: [EMAIL PROTECTED]
On 08/03/2003 06:55:01 AM nolan wrote:
What is the status of dbf2pg. There do not appear
TODO item?
---
Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
On Fri, 2003-08-08 at 16:00, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Seems we have a problem with pooled connections and WITH HOLD
Gathering some of the threads, here's what I see:
1. There is some demand for per database logging. Doing that is rather
beyond the scope of what I intended - in fact what I intended was to enable
sensible log splitting out of band. I'll even write a perl script to do it
for you if you like :-)
Hi there,
At 17:55 05.08.2003, Josh Berkus wrote:
Another way to specify a safe but efficient TRUNCATE ALL command that
might be easier to implement than above TRUNCATE table
[CASCADE|RESTRICT] might be to implement the functionality of the
originally suggested TRUNCATE ALL through a psql
Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
It just seemed complex to figure out which operators needed parens and
which didn't.
The fact that the first attempt was wrong doesn't improve my faith in
that code one bit ;-).
It was posted
If people want to remove a user, I assume they don't want to keep
old objects around.
How about if we created a script that goes through all the databases and
reports items owned by a specific user, or orphaned items not owned by
anyone?
Alvaro Herrera wrote:
Right now the sectors on the hard disk run clockwise, but I heard a rumor that
you can squeeze 0.2% more throughput by running them counterclockwise.
It's worth the effort. Recommended. (Gerry Pourwelle)
In relation to your signature, I assume you have seen this joke:
Hi all,
I've put my hands on 7.4beta1 and it doesn't compile on unixware 7.1.3
(Tom, I know you don't like it)
Here's the logs: I did'nt have enough time to have a closer look, but I
*think* unixware redefines some symbols like shutdown to _shutdown..
Here are the logs
checking build system
--On Friday, August 08, 2003 16:04:47 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
To fix it, remove -K inline from src/port/unixware's CFLAGS.
Dave Prosser of SCO has a fix, but this is the most expedient fix for
now.
Do you think we should make that change
I think we need a more general variable that can take several values,
separated by commas, like:
log_line: dbname,user
or something like that.
In fact, looking at the postgresql.conf file, I see only two setting
that print on every line: log_pid and log_timestamp. Perhaps those two
On Thu, Aug 07, 2003 at 03:43:45PM -0700, [EMAIL PROTECTED] wrote:
I used lcov to generate some fancy webpages that shows code coverage of
PostgreSQL 7.3.4 from running our DBT-2 workload (TPC-C derivative)
against it.
Cool -- one thing I've been meaning to do for a while is to get some code
Christopher Kings-Lynne wrote:
Has anyone reviewed the compatibility list for 7.4 yet?
http://developer.postgresql.org/docs/postgres/unsupported-features-sql99.html
I seem to remember something about us having the unique predicate now or
something? Array support is now better, and cursors?
Already done, but knowing that it's the same on the latest released
compiler is interesting.
I'll pass it on.
LER
--On Thursday, August 07, 2003 16:59:50 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
[EMAIL PROTECTED] writes:
Larry just given me his own compiler and I still have the errors...
Bruce Momjian [EMAIL PROTECTED] writes:
... And of course, we already have pid and timestamp, so once
we are done, we will have seven possible data items on each line, and
with booleans there will be no control over their order on the line.
Which is exactly the way I want it ;-). I can't see
Hi,
I dropped the owner of a table, and now I get this:
pg_dump:
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
I could see that being nice so you could create a couple of different
custom log types, then use one for one database, and another for a
different database.
Point them to different log files and you've got yourself a great
feature.
For people running large numbers of databases on a
1 - 100 of 320 matches
Mail list logo
