---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Hi,
I notice on the SET CONSTRAINTS doc page, it says SET CONSTRAINTS
constraint ...
But it doesn't at all make it clear what constraint is, since cosntraint
names are per-relation I thought?
Chris
---(end of broadcast)---
TIP 9: the planner
Time to install gcc? I believe it's doable for UW.
I haven't touched UW in about 10 years, but I see not much has changed
(I regularly blew up the compiler back then).
andrew
Larry Rosenman wrote:
I managed to blow the SCO compiler up again with /contrib/cube. the
only workaround
(from SCO
Oleg Bartunov wrote:
Bruce, you forgot new contrib/tsearch2 module - full text extension (Oleg,Teodor)
Sorry, added:
New tsearch2 full-text search module (Oleg)
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+
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?
--
Bruce Momjian| http://candle.pha.pa.us
Larry Rosenman [EMAIL PROTECTED] writes:
On Mon, 11 Aug 2003, Bruce Momjian wrote:
Larry Rosenman wrote:
Can we modify pg_dumpall (or pg_dump?) to include a \pset pager off
to prevent the setval() calls from halting an interactive \i of the dump
file?
Your pg_dump's actually invoke the
Actually, your getpwuid_r is the old, pre-POSIX format. The attached
email has the configure tests. I was hoping we wouldn't need them, but
it seems we may.
---
Larry Rosenman wrote:
In src/port, we have in threads.c:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Why is this not together with the mention that dollar signs are *not* allowed
anymore in operator names?
They are in different places because one relates to operator names
(Object Manipulation section) while the other relates to queries
world. It just seemed interesting that the numbers were three times slower
than other databases I ran it on. Here is the script which generates the
You were comparing against databases with similar safety nets to
guarantee against dataloss?
signature.asc
Description: This is a digitally
On Tue, 2003-08-05 at 18:19, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
After the first few sleeps should it add a random() element to the delay
time?
Hmm, that's a thought --- but how big a random element?
Fooling with the original idea, I'm having trouble with getting both
Tom Lane wrote:
I've been thinking about Ludwig Lim's recent report of a stuck
spinlock failure on a heavily loaded machine. Although I originally
found this hard to believe, there is a scenario which makes it
plausible. Suppose that we have a bunch of recently-started backends
as well as
hi...
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 basically had 5M execute statements and
Chris,
SQL_ASCII means that the data could be anything. It could be Latin1,
UTF-8, Latin9, whatever the code inserting data sends to the server. In
general the server accepts anything as SQL_ASCII. In general this
doesn't cause any problems as long as all the clients have a common
Yes.
- Original Message -
From: Jinqiang Han [EMAIL PROTECTED]
Newsgroups: comp.databases.postgresql.hackers
Sent: Thursday, August 07, 2003 11:26 AM
Subject: PITR in 7.4
hi, Tom and Momjian
Is PITR also delayed to 7.5?Right?
3x
Jinqiang Han
[EMAIL PROTECTED]
2003-08-05
-Original Message-
From: Renney Thomas [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 1:43 PM
To: [EMAIL PROTECTED]
Subject: Re: [HACKERS] RE : Oracle to PostgreSQL
What are the legal implications of copying Oracle's own PL/SQL
procedures code and porting them to PgSQL as you
Vadim,
FarewellIt's time for formal acknowledgement that I'm not in The Project
any more.
Bye! Aside from one meeting in 2001, I know you only from your work. But
that's a very lasting impression ... even should you never come back to us, I
think people will still be seeing your name in
No, but I wouldn't bet on DROP DOMAIN uniformly saying domain either.
It's the same code as soon as you get below the top-level command
routine (compare RemoveType and RemoveDomain).
I can't see any conceivable reason to allow this syntax to work!
We are giving zero benefit for a non-zero
Hi all,
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.
CREATE TABLE test ( a integer, b integer );
INSERT INTO test VALUES ( 1 );
CREATE OR REPLACE FUNCTION foo(INTEGER)
RETURNS INTEGER AS'
But that's an additional feature, not a missing feature.
I think the reason we are restrictive about the comparable cases for
relations (pg_class entries) is that we use pg_class entries for a
number of things that users see as unrelated or only weakly related.
For example, indexes are not
Tom Lane wrote:
Andreas Pflug [EMAIL PROTECTED] writes:
Only very-well-documented operators (Chapter 4.1.6) are parens-optimized
(+-*/%);
At the moment ... but you can be sure there will be demand to get smarter.
I never claimed to implement the ultimate solution, just wanted to
The Hermit Hacker wrote:
On Thu, 7 Aug 2003, Bruce Momjian wrote:
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
--On Tuesday, August 05, 2003 11:29:50 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
How is this?
Prevent timestamp from supressing ':00' seconds display
I think that was type interval, not timestamp.
Yeah, it is. (my bad, I think).
LER
regards,
Robert Creager [EMAIL PROTECTED] writes:
Could you supply the relation names corresponding to the relation OIDs
appearing in pg_locks, so we can be sure who's processing what?
Sure, if you tell me how ;-) I looked at the view definition and that didn't help
me much...
select relname from
We could also think about providing an interface to do just Parse,
although this is inessential since you can set up a prepared statement
by PQexec'ing a PREPARE command.
Wait just a minute! phpPgAdmin would love to be able to 'parse' arbitrary
sql entered by the user to separate semi-coloned
I don't think you see what I mean :)
I want to display the data on a webpage to the user. This means that a
varchar containing the string I don't want it, should not appear as I
don''t want it. So pg_escape_string isn't used there. bytea is different
tho because the default display isn't
On Mon, 2003-08-11 at 00:36, Vadim Mikheev wrote:
It's time for formal acknowledgement that I'm not in The Project any
more.
I'm not interested in small features/fixes and have no time for big
ones.
It was this way for very long time and I don't see how/when that could
change.
My
I thought that statement level triggers did not work yet.
Are they supposed to work in 7.4?
(But even if they don't work they shouldn't crash...)
elein
On Sun, Aug 03, 2003 at 08:04:11PM -0700, Joe Conway wrote:
I was working on trigger support for PL/R and ran across this bug in my
own code
Andi,
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 meta-command. Any
suggestions for a safe
On Tue, Aug 12, 2003 at 04:01:33PM -0400, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Can I have a TODO for this?
* Prevent accidental re-use of sysids for dropped users and groups
The other part of the thread was something like
* Prevent dropping user that still owns
I propose that the following should be added to the TODO list:
- expose read-only NEW/OLD rowsets in statement-level triggers that
represent the affected rows.
- Implement a way to enable triggers to check which columns are affected
by the triggering statement.
Regards,
Andreas
following is taken from postgresql-7.3.2/src/backend/storage/lmgr/readme:
If we are setting a table level lock
both the blockId and tupleId (in an item pointer this is called
the position) are set to invalid, if it is a page level lock the
blockId is valid, while the
Seems to be OK. See below.
BTW, for those interested, following up a note from Joe Conway I
discovered yesterday the Right Way (tm) to build RPMs (nothing Pg
specific in this). Basically, you set up some rpm macros like this in
~/.rpmmacros:
%_topdir%(echo ${HOME}/rpm)
%_tmppath
Using the attached script, the build fails while trying ot tar up the
distributions ... when its trying to build the tools tar file, error being
that it can't find the src/data directory ... compared against the
snapshot build script, it doesn't look like I've missed anything, and i
haven't
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. However, are the other field types for which
we have to do this? Can you put nulls and stuff in text/varchar/char
fields?
Hi,
In phpPgAdmin, we automatically set the HTML page encoding to and encoding
that allows us to properly display the encoding of the current postgresql
database. I have a small problem with SQL_ASCII. Theoretically (and what
we currently do), we should set page encoding to US-ASCII. However,
Christopher Kings-Lynne writes:
The most useful reason (and I wish you could turn it on with psql file) is
the line number in the file where any errors occur.
psql -f file will do that.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of
I forgot to update the typedefs for 7.4 before running pgindent. I
would like to run it again, hopefully soon. It shouldn't change very
much at all, but will recognize more of the typedefs.
OK?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
No, the one where we always print hh:mm:ss for an interval, even if seconds
is zero.
--On Tuesday, August 05, 2003 01:03:57 -0400 Bruce Momjian
[EMAIL PROTECTED] wrote:
I don't know about that item. There is a menion of allowing 60 seconds
--- is that it?
I think the new pg_get_triggerdef and pg_constraint_is_visible functions
aren't mentioned.
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Larry Rosenman [EMAIL PROTECTED] writes:
cc -O -K inline -g -I../../../../src/include -I/usr/local/include -c -o
printtup.o printtup.c
UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled
UX:acomp: ERROR: printtup.c, line 94: undefined struct/union member:
_shutdown
I thought some of you might find this interesting in light of recent issues
with SCO cc:
http://gcc.gnu.org/ml/gcc-patches/2003-08/msg00191.html
In short, the FSF is discussing the possibility of dropping support for SCO
Unix in GCC.
---(end of
Andrew Dunstan wrote:
I did have a thought that it could be done lazily (on backend startup)
on other databases and immediately on the current database. I guess it
depends on the cost of checking for such things - wouldn't want to add
greatly to startup time.
That would leave a small window
Robert Creager [EMAIL PROTECTED] writes:
[much data]
Well, I'm baffled. The vacuum process is evidently waiting for the
insert, but I don't think it could be holding any lock that the other
two want. The insert is trying to grab a per-buffer lock, which is
reasonable. I do not see that the
Bruce Momjian [EMAIL PROTECTED] writes:
Adding several new variables is fine, but what do we call the hostname
option if we already have log_hostname?
shrug We've renamed GUC variables before for consistency. I'd opt
for picking names that show the common purpose, maybe log_line_FOO?
On Tue, 2003-08-12 at 15:36, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
I wasn't interested in measuring the performance of yacc -- since I know
it is bad. It was a basic test which wasn't even meant to be real
world. It just seemed interesting that the numbers were three times
elein wrote:
I thought that statement level triggers did not work yet.
Are they supposed to work in 7.4?
(But even if they don't work they shouldn't crash...)
Yeah, they work - not as everyone would like, but they work. All fixed
now anyway.
Joe
---(end of
Josh Berkus wrote:
Joe,
They are done (at least the array declarations and array element
assignment part):
Way cool! How'd I miss that one?
Time to test
o Add PL/PgSQL PROCEDURES that can return multiple values
Hmmm ... I know how this got on the TODO, but it's
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Ah OK, I must have been thinking of the database owner check. I'd vote for
(1) checking that they own no objects and by default owning all their stuff
to the database owner. Plus add an optional clause:
DROP USER foo OWNER TO bob;
If you can
-Original Message-
From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED]
Sent: 11 August 2003 04:02
To: Andrew Dunstan; Hackers
Subject: Re: [HACKERS] dropping a user causes pain (#2)
DROP USER foo OWNER TO bob;
Isn't that a bit tricky as foo might own objects in other
(Thought triggered by something Tom said the other day)
Is this a security hole? Looks like one to me. Would it be better to use
a sequence generator for sysids instead of using max+1 on the user
table? Or else store the last sysid used somewhere?
andrew
facetest=# create user blurfl;
CREATE
* Tom Lane ([EMAIL PROTECTED]) wrote:
Stephen Frost [EMAIL PROTECTED] writes:
You probably know but I'll quickly outline it to point out the
differences, as I see them, from the 'COPY' ability. Basically the user
defines their own C structure and then malloc's an array of them. The
user
elein [EMAIL PROTECTED] writes:
This is as far as I've gotten with 7.4.
Would you rebuild with --enable-debug (perhaps also --enable-cassert)
so that the gdb backtrace is more informative?
Also, it seems likely that the issue is in or around the recently-added
IPv6 support, so I'd suggest using
Rod Taylor wrote:
-- Start of PGP signed section.
Allow SQL200X inheritance syntax LIKE subtable, INCLUDING DEFAULTS?
(Rod)
Yes, it includes defaults.
OK, updated.
Have COMMENT ON DATABASE on non-local database generate a warning
(Tom)
I think that was someone else's work ... Rod
Tom Lane wrote:
I'm beginning to think that was a serious omission. I'm tempted to fix
it, even though we're past feature freeze for 7.4. Comments?
Seems pretty well isolated. If you're tallying votes, count me as a yay.
Joe
---(end of
I managed to blow the SCO compiler up again with /contrib/cube. the only
workaround
(from SCO already) is to disable -O on that module.
Fair warning.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail:
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
hash_search() suggests that
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (Bruno Wolff
III) transmitted:
On Fri, Aug 08, 2003 at 15:32:05 +0530,
Rahul_Iyer [EMAIL PROTECTED] wrote:
hi, im currently working on a project that requires batch
operations - eg. Batch insert/update etc. The database
I just (with the last half hour) grabbed a fresh copy of 7.4 from CVS
and got an error when building contrib/array:
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I.
-I../../src/include -c array_iterator.c -o array_iterator.o
array_iterator.c:30: utils/fmgroids.h: No such
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 basically had 5M execute statements and
Tom Lane wrote:
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
Stephen Frost [EMAIL PROTECTED] writes:
... If libpq grabs the entire result in one go then that may
actually cause a problem for me when I start to move things from Oracle
to postgres since the clients don't always have much memory available.
It does that in an ordinary SELECT. The customary
Below is output from 7.3 pg_dump that is being loaded into 7.4 beta1.
It would seem that revoking the permissions of the owner doesn't work
out so well.
r=# CREATE FUNCTION weekdate (date) RETURNS timestamp with time zone
r-# AS '
r'# SELECT cast(to_date(''01 01 ''|| extract(''year'' FROM
I know. It just makes a few things a pain if you can't say I know this
character can't be part of that.
Nevermind. Just wishful thinking. I'll shut up now.
andrew
Christopher Kings-Lynne wrote:
Seriously, I think there's a good case for banning a few characters in
at least some names - like
Bruce Momjian [EMAIL PROTECTED] writes:
Can I have a TODO for this?
* Prevent accidental re-use of sysids for dropped users and groups
The other part of the thread was something like
* Prevent dropping user that still owns objects, or auto-drop the objects
which if successful would eliminate
I blame SuSE.
Thank you for the fix and confirmation of the problem.
elein
On Mon, Aug 11, 2003 at 01:53:31PM -0400, Tom Lane wrote:
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
Sla,
PS : why limitation to 8 patrameters in stored procedures ??
What version of PostgreSQL are you using?
The limit is 16 parameters for 7.1 and 7.2, raised to 32 parameters in 7.3 and
after. Further, you can raise the limit yourself at compile-time, although
I understand it incurrs
--On Wednesday, August 06, 2003 12:11:24 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
cc -O -K inline -g -I../../../../src/include -I/usr/local/include -c -o
printtup.o printtup.c
UX:cc: WARNING: debugging and optimization mutually exclusive; -O
disabled
I don't know about that item. There is a menion of allowing 60 seconds
--- is that it?
---
Larry Rosenman wrote:
What about the interval change in ISO datestyle for zero seconds?
LER
--On Sunday, August 03, 2003
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, and I don't recall seeing it before.
I can still connect on IP4 socket and
The first beta fails two regression tests
on alphaev67-dec-osf4.0g, compiled by cc -std -std
i.e. Compaq/HP Digital Unix/Tru64/name-of-the-day
They are join (FAILED) and random (failed ignored). Attached is the
regression diff.
During configuration a warning stated that our version of Bison was
I'm working on writing a script that automatically tests all the
built-in functions. As a first step, I just passed NULL for all
of the arguments for each built-in function. I've attached a
list of the 90 functions that crash the backend when this is done.
Since the culprit functions all seem
Andreas Pflug [EMAIL PROTECTED] writes:
Is it useful to allow these special chars at all? Seems this creates a
lot of work, and most admins will probably stick to normal user names
anyway.
Well, the reason it's been left unfixed for so long is exactly that it
didn't seem pressing. But if
Sorry List.
I´ve sent a message to unsubscribe to the wrong
address. The message was for unsubscribe from the
digest list.
Sorry.
Rgs,
Antonio Belloni
___
Conheça o novo Cadê? - Mais rápido, mais fácil e mais preciso.
Toda a
* Tom Lane ([EMAIL PROTECTED]) wrote:
Of course the obvious way of getting rid of the parser overhead is not
to parse everytime --- viz, to use prepared statements.
I think this would be nice to have too... On a similar note (I think
anyway) I wasn't able to find any functions for bulk dumps
Here is Dave's reply re: -K no_host vs. removing -K inline. (I.E. ADDING
-K no_host vs. removing -K inline:
---Dave Prosser:
I had someone ask about performance impact. I gave him the alternate
-Kno_host as well.
Do you have a feel for what it would do to/for us?
There are only a few places
I don't use -g
I'm trying now on your machine Larrye,
If you want to have a look
On Thu, 7 Aug 2003, Larry Rosenman wrote:
Date: Thu, 07 Aug 2003 15:56:58 -0500
From: Larry Rosenman [EMAIL PROTECTED]
To: Tom Lane [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc: pgsql-hackers list [EMAIL PROTECTED]
This is caused by sys/socket.h #defining shutdown _shutdown, and already
reported.
I filed the bug last nite, and Tom replied, and my reply is in the thread.
LER
--On Wednesday, August 06, 2003 19:14:49 +0200 [EMAIL PROTECTED] wrote:
Hi all,
I've put my hands on 7.4beta1 and it doesn't
I'm looking over the last bits of translations of pg. Is it to late to
update the translations for 7.4? Should I work on the cvs head version or
is there some branching going on?
--
/Dennis
---(end of broadcast)---
TIP 7: don't forget to
Sean Chittenden [EMAIL PROTECTED] writes:
I'm beginning to think that was a serious omission. I'm tempted to
fix it, even though we're past feature freeze for 7.4. Comments?
On a quasi-similar note (and unless I've missed how to do this), you
can't create a cursor from a prepared statement,
Andreas Pflug [EMAIL PROTECTED] writes:
Only very-well-documented operators (Chapter 4.1.6) are parens-optimized
(+-*/%);
At the moment ... but you can be sure there will be demand to get
smarter.
regards, tom lane
---(end of
On Tue, Aug 12, 2003 at 07:00:35PM +0200, [EMAIL PROTECTED] wrote:
how far have you got with statement-level triggers development?
In PostgreSQL 7.3, statement-level triggers are not supported. In 7.4,
you can define statement-level triggers in C, PL/PgSQL, PL/Python, and
PL/Tcl. One piece of
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Bruce Momjian writes:
If a file is needed by three non-backend directories, /port seems to be
the proper place for it.
src/port is intended for replacement implementations of standard library
functions.
I concur, src/port
I said:
I doubt a hash is worth maintaining, because the active tabstat entries
should only be for tables that are being touched in the current command
(thus, there are not more than six in your example). I'm not sure why
it takes so much time to look through six entries though ...
I
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Will DROP TYPE automatically handle dropping constraints and dependent
columns properly?
Sure. Once you get down to the dependency-chaser, a type is a type.
Will all its messages use the word 'domain' and not
'type'?
No, but I wouldn't bet
No, I don't think any of that was done, particularly because there was
no discussion of the implemention.
---
Hannu Krosing wrote:
Tom Lane kirjutas R, 08.08.2003 kell 16:56:
Bruce Momjian [EMAIL PROTECTED] writes:
Bruce Momjian [EMAIL PROTECTED] writes:
Yes, I have been thinking of that. The big question is whether a
non-super user can control the reset value?
He could (via PGOPTIONS) ... but since he can only increase it, there is
nothing to fear.
regards, tom lane
--On Tuesday, August 05, 2003 16:41:34 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
--On Tuesday, August 05, 2003 16:27:55 -0400 Tom Lane
[EMAIL PROTECTED]
A variant (which'd be okay with me) is to separate these fields with
tabs instead of spaces; then the
Hi all,
I have produced some code coverage data using gcov + ltp to show which
parts of the source code the regression tests are hitting and which parts
they aren't. The results are at: http://www.alcove.com.au/pgregress/
Thanks,
Gavin
---(end of
hi, Tom and Momjian
I wonder if 7.4 will have win32 porting
I checkout source from cvs. I only find win32 makefile for client.
Jinqiang Han
[EMAIL PROTECTED]
2003-08-05
---(end of broadcast)---
TIP 4: Don't
Tom Lane [EMAIL PROTECTED] 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 bar();
bar
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
gcc -pipe -O -Wall -Wmissing-prototypes -Wmissing-declarations -Wno-error -I
./../include -I. -I../../../../src/include -DMAJOR_VERSION=3 -DMINOR_VERSIO
N=0 -DPATCHLEVEL=0 -DINCLUDE_PATH=\/home/chriskl/local/include\ -c -o
preproc.o
Peter Eisentraut [EMAIL PROTECTED] writes:
I propose to add the following macros for the fields of an error or notice
message for use in libpq applications.
Where, in libpq-fe.h?
The proposed names look fine to me except for
W PG_DIAG_STACK_TRACE
This seems overly specific to my eyes
That line is certainly strange:
#0 0x40099ac5 in dllname () from /usr/lib/libwsock32.so
When you run configure, it says you are on Linux, right?
My guess is that gdb is getting confused because there is no dllopen
call in StreamServerPort().
On Sun, 10 Aug 2003, Vadim Mikheev wrote:
FarewellIt's time for formal acknowledgement that I'm not in The Project any more.
I'm not interested in small features/fixes and have no time for big ones.
It was this way for very long time and I don't see how/when that could change.
My
Oh yea, I'm running 7.3.3 on Redhat 7.3.
--Nate
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Vadim Mikheev wrote:
(B
(B It's time for formal acknowledgement that I'm not in The Project any
(B more.
(B
(B I'm not interested in small features/fixes and have no time for big
(B ones.
(B It was this way for very long time and I don't see how/when that could
(B change.
(B
(B My
Mendola Gaetano [EMAIL PROTECTED] writes:
Incredible to believe but after playng around that funcion started
to work. I'm not crazy.
Yeah, it was a problem with storing into a possibly-obsolete pointer ---
the visible effects could range from nothing to a core dump depending on
whether the
Hello:
I'm trying to establish a TLS connection to PostgreSQL 7.4 beta 1 on
windows and Cygwin using C#, i have configured PostgreSQL as it's
explained here:
http://developer.postgresql.org/docs/postgres/ssl-tcp.html
There are anything more that is needed to be done in order to run
SSL/TLS
--On Friday, August 08, 2003 15:31:09 -0500 Larry Rosenman [EMAIL PROTECTED]
wrote:
The fix won't be out until Update Pack 3 at least (which is 3 months
away). It **MIGHT** make an update pack but I don't know.
I meant Maintenance Pack. The difference is the Update Packs cost a
subscription
Allow SQL200X inheritance syntax LIKE subtable, INCLUDING DEFAULTS?
(Rod)
Yes, it includes defaults.
Have COMMENT ON DATABASE on non-local database generate a warning
(Tom)
I think that was someone else's work ... Rod maybe?
Name removed. Anyone know?
I sent in a patch, but it was
101 - 200 of 320 matches
Mail list logo
