On Fri, 15 Aug 2003, Christopher Kings-Lynne wrote:
> > > I can also attest to the horrendously long time it takes to restore the
> ADD
> > > FOREIGN KEY section...
> >
> > That really needs to be rewritten to do a single check over the table
> > rather than running the constraint for every row.
On Fri, 15 Aug 2003, Gavin Sherry wrote:
> On Thu, 14 Aug 2003, Stephan Szabo wrote:
>
> > That really needs to be rewritten to do a single check over the table
> > rather than running the constraint for every row. I keep meaning to get
> > around to it and never actually do. :( I'm not sure tha
Something odd going on with the list - I never saw the original that Chris is
replying to.
Philip.
On Fri, 15 Aug 2003 12:22 pm, Christopher Kings-Lynne wrote:
> I've been doing all my freebsd/alpha build with --enable-thread-safety for
> weeks and I haven't seen any compile or running problems.
On Fri, 15 Aug 2003, Christopher Kings-Lynne wrote:
>
> > > I throw last nights backup at it. Data went in in about 1/2 an hour then
> the
> > > constraints went in and they took at age. about 2 hours.
> > > Is there anyway to speed up the database constraint code? Because quite
> > > frankly
(Responding to the deafening silence regarding my posts a couple of days
ago about logging dbnames and disconnections) ;-)
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,
I'm using 7.3.3 of the server, and pg73b1jdbc2.jar for the JDBC driver.
Various permutations of calls to the setTransactionIsolation all fail to
yield a driver state that will tell me that it is set up for
serializable transactions.
Help!?
I googled, I grepped. I find mention of problems with re
You can actually kinda hack this by going:
SELECT 41235125::abstime::timestamp;
Where 41235125 is a unix epoch.
Cheers,
Chris
- Original Message -
From: "David Fetter" <[EMAIL PROTECTED]>
To: "PG Hackers" <[EMAIL PROTECTED]>
Sent: Friday, August 15, 2003 4:46 AM
Subject: [HACKERS] New
> > I throw last nights backup at it. Data went in in about 1/2 an hour then
the
> > constraints went in and they took at age. about 2 hours.
> > Is there anyway to speed up the database constraint code? Because quite
> > frankly at the current speed your probably better off without the
> > co
Not quite the same - timestamps and pids have known formats, while db
names are almost arbitrary. I know including spaces in names is horrible
to my *nix way of thinking, but others might not have my prejudices.
(interesting question - what characters are NOT allowed in a database
name?).
BTW,
On Tue, 5 Aug 2003, The Hermit Hacker wrote:
>
> 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 does
BTW, the init file has this:
# chkconfig: - 85 15
I would modestly suggest changing this to something like 81 19. The
reason - these are the same settinga as httpd, and I normally want Pg
started up before the web server and shut down after the web server.
andrew
Andrew Dunstan wrote:
Seems
How are statement level triggers supposed to work? Are they just
triggers deferred until the end of the statement? You mentioned access
to the affected rows, but I don't understand how that is supposed to
happen.
---
Andr
On Mon, 2003-08-04 at 21:46, Christopher Kings-Lynne wrote:
> Hi,
>
> Is it possible to get a default value on a boolean column to be anything
> other than 't', 'f', true or false?
NULL of course :) 1 or 0 also works.
And regardless of how hard MS Access tries, -1 is not true.
signature.asc
D
On Thu, Jul 31, 2003 at 05:06:12PM -0400, Tom Lane wrote:
> Alvaro Herrera Munoz <[EMAIL PROTECTED]> writes:
> > $ createlang -d alvherre plpgsql
> > createlang: language installation failed: ERROR: c: permission denied
> > What's the "c" it's complaning about?
>
> The C procedural language, pres
Peter Eisentraut wrote:
> Tom Lane writes:
>
> > I was afraid it was something like that. Can we leave the directory
> > structure as-is and just make the .o (and .d) files get built in the
> > upper directory, that is
> > gcc ... -o english_stem.o snowball/english_stem.c
>
> That will fail
[EMAIL PROTECTED] writes:
> I've just tried the cvs on uw 7.13. It fails on compiling hba.c:
> UX:acomp: ERROR: "hba.c", line 651: undefined symbol: AI_NUMERICHOST
> UX:acomp: ERROR: "hba.c", line 1237: undefined symbol: AI_NUMERICHOST
This seems similar to Weiping He's problem on AIX. As I said
Done, now:
Allow thread-safe libpq with --enable-thread-safety (Lee
Kindness, Philip Yarra)
---
Lee Kindness wrote:
> Bruce, I know it's a bit picky but both below should be along the
> lines of "Allow th
Dann Corbit wrote:
> > Perhaps by 7.5 we can enable the above logic by default.
> >
> > However, I do think we will have to mention the platforms
> > that aren't thread-safe some day, of course, once we enable
> > thread-safe by default.
>
> Perhaps a portable BSD licensed threading library cou
Gavin Sherry <[EMAIL PROTECTED]> writes:
> Neither. I might look into it further later, but here's a patch to exit
> out of pgstat_initstats() if we're not collecting stats (attached).
Applied along with other fixes.
regards, tom lane
---(end of br
В Втр, 05.08.2003, в 05:23, The Hermit Hacker пишет:
> /usr/bin/cvs -d /cvsroot -q checkout -rREL7_4_BETA1 -P pgsql
> /usr/bin/find pgsql -type d -name CVS -print | xargs rm -rf
Hint: cvs export
--
Markus Bertheau <[EMAIL PROTECTED]>
signature.asc
Description: =?koi8-r?Q?=FC=D4=C1?= =?koi8-r?
vajjhala wrote:
> HI
>
> I am running MFcobol on a linux machine which is
> having Postgresql. can I access pgsql database thru
> mfcobol.
> If it is possible where can I get odbc drivers and
> what is the procedure help me
This is probably not helpful, but FWIW I've written a driver for AcuCorp
An alternative might be something that postprocesses the output from
pg_dump into, say, XML. I've been thinking about that. I might put it
on my todo list.
andrew
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
It just seemed complex to figure out which operators needed parens an
[EMAIL PROTECTED] writes:
> UX:acomp: ERROR: "fe-protocol3.c", line 1402: internal compiler error: can't deal
> with op BMOVE
I think you need a compiler with fewer internal errors ;-). Is there an
update available?
regards, tom lane
---(end of
> To forestall this scenario, I'm thinking of introducing backoff into the
> sleep intervals --- that is, after first failure to get the spinlock,
> sleep 10 msec; after the second, sleep 20 msec, then 40, etc, with a
> maximum sleep time of maybe a second. The number of iterations would be
> redu
I've been doing all my freebsd/alpha build with --enable-thread-safety for
weeks and I haven't seen any compile or running problems...
Configure doesn't see it tho:
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking for strerror_r... yes
Bruce Momjian wrote:
How are statement level triggers supposed to work? Are they just
triggers deferred until the end of the statement? You mentioned access
to the affected rows, but I don't understand how that is supposed to
happen.
I'm not sure this is a fair assessment of statement level trigg
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 rule for DBAs would be "don't allow
>> tabs in db/user names".
> Tabs
Andreas Pflug wrote:
> Bruce Momjian wrote:
>
> >It might be a bit risky getting pg_dump to use it though?
> >
> >
> >
> >I don't think we every want pg_dump to use it --- better accurate than
> >pretty in there.
> >
> Agreed.
>
> > There seems to be some tough assumptions that have to
> >be m
"Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> What about use the same algorithm used in ethernet when a collision is
> detected?
Random backoff is what Rod suggested, but I don't care for the ethernet
method in detail, because it allows for only a fairly small number of
retries before giving up.
Bruce Momjian writes:
> Lee Kindness wrote:
> > Bruce, the changes you made yesterday to configure for
> > --enable-thread-safety have broken the build, at least for Linux on
> > Redhat 9.
> OK, how did I break things? Can you show me the failure.
After a:
./configure --prefix=/var/lib/pg
My issue is that I think there are reasonable people might want
username, dbname, hostname, host ip, and host port on the log lines.
This is the information that we currently report during a connection, if
enabled.
I have no problem adding those five booleans if people prefer booleans
--- my big
Larry just given me his own compiler and I still have the errors...
On Thu, 7 Aug 2003, Tom Lane wrote:
> Date: Thu, 07 Aug 2003 16:49:41 -0400
> From: Tom Lane <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: pgsql-hackers list <[EMAIL PROTECTED]>
> Subject: Re: [HACKERS] build on unixware 713
>
Agreed. I have been using ecpg a little and it is really great.
---
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Does anyone mind if I remove src/interfaces/cli? It's clearly outdated
> > and useless.
Christopher Kings-Lynne wrote:
> Hi guys (tom),
>
> Just reminding people that there was a question regarding my changes to
> psql's \d command. I'm not sure if everyone wanted all the identifier
> names double quoted or not...
I assume we don't want them always quoted.
> And are people happy w
>
> 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
>
I'm observing the same pretty odd behavior.
Do we both expect something wron
It all built and passes regressions for me on freebsd/alpha, I got this
though:
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\
Bruce Momjian wrote:
Still, if there's something not precise, it should be cleared. Which
tough assumptions are made that seem doubtful to you?
It just seemed complex to figure out which operators needed parens and
which didn't.
Only very-well-documented operators (Chapter 4.1.6) a
Tom Lane wrote:
Bertrand Petit <[EMAIL PROTECTED]> writes:
And I just got another one, much simpler, that failed the same
way with the same data set:
UPDATE rimdb_atitles SET aka_title=convert(byte_title,charset,'UTF8');
[ where rimdb_atitles has an index on column "attribs varchar[]" ]
Uh
Joe Conway wrote:
> 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.use
[EMAIL PROTECTED] writes:
> Larry just given me his own compiler and I still have the errors...
[experiments a little...] Hmm. It works okay with -g, but fails with
-O.
I suggest filing a bug report. I'm not planning to spend any time
looking for workarounds for SCO's compiler bugs.
Thanks to Tom and Bruce, we can now compile CVS 7.4 on UnixWare with OUT
any tweaks, including
the --enable-thread-safety switch.
Here is what I used, and is now running on lerami:
CC=cc CXX=CC ./configure --prefix=/usr/local/pgsql --enable-syslog \
--with-CXX --enable-multibyte --enable
On Thu, 7 Aug 2003, 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
Brain thinking one thing,
It's easier to create a simple pgsql function
to do this ...
johnl
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of The Pennant Shop
> Sent: Wednesday, August 06, 2003 2:06 PM
> To: [EMAIL PROTECTED]
> Subject: [HACKERS] Select distinct question ... co
Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > It might be a bit risky getting pg_dump to use it though?
>
> I definitely don't want pg_dump using the pretty-print stuff ;-).
> I'm neutral on whether to use it in psql's \d commands.
I thought the pretty-printing stuff w
Larry, haven't managed to look at that patch... But stuffed for time
just now - just about to head off for the weekend. I'm hoping to spend
a bit of time on this on Tuesday! So, i'll see how things have
progressed then.
L.
Larry Rosenman writes:
> --On Friday, August 08, 2003 11:53:34 +0100 Lee
This is the situation, I create a user called "
test=# create user ;
CREATE USER
test=# drop user ;
DROP USER
test=# create user ;
CREATE USER
test=# create table temp(a int4);
CREATE TABLE
test=# grant select on temp to ;
GRANT
test=# \dp temp
Access privileges for
--On Saturday, August 09, 2003 18:57:10 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
Larry Rosenman <[EMAIL PROTECTED]> writes:
Ok, with using OUR src/port/getaddrinfo.c (by #undef'ing
HAVE_GETADDRINFO and adding getaddrinfo.o to Makefile.global's LIBOBJS,
it works again.
We need to devise a con
Sean Chittenden <[EMAIL PROTECTED]> writes:
> indexCorrelation is 1.0 for the 1st key in a multi-column index.
... only if it's perfectly correlated.
> As things stand, however, if a multi-column key is
> used, the indexCorrelation is penalized by the size of the number of
> keys found in the mul
Christopher Browne wrote:
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 i
Carlos,
On Fri, Aug 08, 2003 at 09:20:01AM +0200, Carlos Guzman Alvarez wrote:
> >I want to know if postgresql 7.4 beta 1 can be configured under
> >Cygwin with SSL support ??
> >
> >If the answer is positive how can i do it ?? or where can i found
> >documentation about this ( under linux or cygw
> 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...
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
On Sat, 09 Aug 2003 20:12:36 -0400
Tom Lane <[EMAIL PROTECTED]> said something like:
> Robert Creager <[EMAIL PROTECTED]> writes:
> > Anything to look at before I kick it?
>
> pg_locks and pg_stat_activity, if you can select from them in a
> non-stuck backend.
tassiv=# select * from pg_locks;
r
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Yes, thread.c, path.c, and sprompt.c should be in utils, but how do I do
> > that? Utils seems to be a place things are pulled from, rather than a
> > library that goes with every link.
>
> > Is it worth creating another library that
"Tom Lane" <[EMAIL PROTECTED]>
> 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
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 tuple
I get the error message below when trying to make inside of the contrib
subdirectory. It was happening last night as well. I removed all of the
source and got a clean copy about an hour ago and am still having the
problem.
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../src/inter
Bruce,
> > Actually, now that I look at it again, it is referring to procedures,
> > not functions. Maybe just make it:
> >
> > o Add capability to create and call PROCEDURES
OK. I need to put a full proposal behind this once 7.4 is in the can.
However, this is largely academic until we get
--On Saturday, August 09, 2003 12:26:06 -0500 Larry Rosenman
<[EMAIL PROTECTED]> wrote:
--On Saturday, August 09, 2003 11:47:43 -0500 Larry Rosenman
<[EMAIL PROTECTED]> wrote:
I tried(!) to load my 7.3.4 data into 7.4CVS.
the Bricolage folks have managed to make a circular definition (at lea
On Fri, 8 Aug 2003 11:06:56 -0700, Sean Chittenden
<[EMAIL PROTECTED]> wrote:
>[...] it'd seem as though an avg depth of
>nodes in index * tuples_fetched * (random_io_cost * indexCorrelation)
>would be closer than where we are now...
Index depth does not belong here because we walk down the index
OK,
So if you agree that there is a quoting problem,and you don't mind
breaking backwards compatibility for it, I'll do a complete patch...
Chris
On Fri, 8 Aug 2003, Tom Lane wrote:
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > The situation seems to be a bug that this patch would
I just committed another pgindent run with updated typedefs.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square,
I tried(!) to load my 7.3.4 data into 7.4CVS.
the Bricolage folks have managed to make a circular definition (at least
not loadable).
why does each setval() call invoke the pager?
the dump I used is at:
http://www.lerctr.org/~ler/pg.dump.gz
$ ls -l pg.dump*
-rw-r--r--1 ler isis
--On Friday, August 08, 2003 15:02:47 -0400 Andrew Dunstan
<[EMAIL PROTECTED]> wrote:
I'm curious to know what that will do to performance.
It just removes the ability to inline some functions. The other option is
to
add -K no_host, which will prevent strcpy() and friends from being inlined,
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, they
> are generic sorting routines.
PostgreSQL u
On Sat, 09 Aug 2003 21:17:05 -0400
Tom Lane <[EMAIL PROTECTED]> said something like:
> Robert Creager <[EMAIL PROTECTED]> writes:
> > [much data]
>
> Could you supply the relation names corresponding to the relation OIDs
> appearing in pg_locks, so we can be sure who's processing what?
>
Well,
Alexey Mahotkin <[EMAIL PROTECTED]> writes:
> Where is the actual code for (rudimentary) Unicode collation?
strcoll() and friends, in libc. If you aren't happy with the sorting
and case translation behavior, you've selected the wrong locale.
regards, tom lane
---
"Vadim Mikheev" <[EMAIL PROTECTED]> writes:
> FarewellIt's time for formal acknowledgement that I'm not in The Project an=
> y more.
Just a "me too" ... we'll all miss you. Thanks so much for all the work
you have put into Postgres. And best of luck in your future activities.
On Mon, 11 Aug 2003, Dave Page wrote:
> Remind me never to get a job where you work :-)
Out of the 6 years I was at the university, I can think of but three ppl
who left that I can sincerely say I was sad to see leave ...
---(end of broadcast)---
On Mon, 11 Aug 2003, Andrew Dunstan wrote:
>
> - Original Message -
> From: "Gavin Sherry" <[EMAIL PROTECTED]>
> > I am still researching ways of increasing performance of yacc parsers --
> > there is a very small amount of information on the Web concerning this --
>
> I know some peopl
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?
Thanks,
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail:
Tom Lane writes:
> Looking at the CVS history, it seems that Lockhart had an idea of
> building a CLI-spec-compatible interface on top of ecpg, but never
> went further than an initial commit.
CLI is ODBC, not ecpg.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of bro
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 of orphanage for existing
Vadim, sorry to see you go. You baled me out of a lot of difficult
problems. Thanks.
---
Vadim Mikheev wrote:
> FarewellIt's time for formal acknowledgement that I'm not in The Project any more.
>
> I'm not interested in
> In both cases ANALYZE will calculate correlation 1.0 for column X,
> and something near zero for column Y. We would like to come out with
> index correlation 1.0 for the left-hand case and something much less
> (but, perhaps, not zero) for the right-hand case. I don't really see
> a way to do
Strike that, the how to run message comes at the end of initdb, not
install... Maybe we need a message after install telling newbies like
myself to run initdb... :-P
Robert Treat
On Tue, 2003-08-12 at 09:58, Robert Treat wrote:
> IIRC the message at the end of install used to echo out the startu
Makes sense, but I think DROP USER should also warn immediately if it
detects the most common case (I imagine) where the user owns things in
the current database.
andrew
Bruce Momjian wrote:
If people want to remove a user, I assume they don't want to keep
old objects around.
How about if we c
ISTM there's a difference between an object without an (exisiting) owner
and an object whose owner doesn't currently have the privileges required
to create it, although maybe there's a good case for a script to detect
the latter as a part of a good administrator's arsenal of tricks in
keeping t
Shachar Shemesh <[EMAIL PROTECTED]> writes:
> Also, I think a pretty simple workaround would be to have
> PSQL search for the upper case identifier, and if not found, search for
> the lower case. This should allow a migration path while the tools and
> functions are being translated (and should,
Christopher Kings-Lynne writes:
> Has anyone reviewed the compatibility list for 7.4 yet?
Yes.
> I seem to remember something about us having the unique predicate now or
> something?
It's not there yet.
> Array support is now better,
But not good enough.
> and cursors?
Same.
> String ops f
Christopher Kings-Lynne 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.
The reason none of this will work is that users are global, so when you
drop a user,
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> I assume his point is "how do we set all of a user's constraints deferred by
> default"?
[shrug] We tell the user to create 'em that way in the first place.
regards, tom lane
---(end of broad
> I can think of a number of ways we might attack this, but none seem
> especially attractive ---
>
> 1. Have the index AMs create and switch into a special memory context
> for each call, rather than running in the main execution context.
> I am not sure this is workable at all, since the AMs ten
Joe Conway <[EMAIL PROTECTED]> writes:
> 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".
Well, the early voting
> Rod Taylor <[EMAIL PROTECTED]> writes:
>> Do you happen to have any numbers comparing prepared inserts in a single
>> transaction against copy?
> COPY is about a factor of 6 faster, it appears. I got 11.8 versus
> 1.87 seconds for loading the same amount of data (with the 3-column
> test table)
Using
Mac OS X 10.2.6
Pgsql 7.4 (postgresql-7.4beta1) from postgresql.org
devpgjdbc2.jar
and WebObjects 5.2
I get
LOG: invalid message length
when EOModeler creates my database.
When I built PostgreSQL I specified
--with-pam --without-readline
Since I don't have ant the "--wit
Rod Taylor <[EMAIL PROTECTED]> writes:
> r=# REVOKE ALL ON FUNCTION weekdate (date) FROM PUBLIC;
> REVOKE
> r=# GRANT ALL ON FUNCTION weekdate (date) TO PUBLIC;
> GRANT
> r=# REVOKE ALL ON FUNCTION weekdate (date) FROM rbt;
> ERROR: dependent privileges exist
> HINT: Use CASCADE to revoke them to
elein <[EMAIL PROTECTED]> writes:
> It sounds like Joe's guess on this was right.
I've committed this fix in configure.in:
***
*** 631,637
AC_CHECK_LIB(gen, main)
AC_CHECK_LIB(PW, main)
AC_CHECK_LIB(resolv, main)
- AC_CHECK_LIB(wsock32, main)
AC_SEARCH_LIBS
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? String ops for LOBs?
Chris
---
I never know what to say in response to stuff like this ... its like
having to sign a card when a co-worker leaves ... then again, unlike most
co-workesr, I can definitely say its been a great pleasure to have known,
and worked, with you ... you brought, and gave, alot to the project, and
for that
Bertrand Petit <[EMAIL PROTECTED]> writes:
> And I just got another one, much simpler, that failed the same
> way with the same data set:
> UPDATE rimdb_atitles SET aka_title=convert(byte_title,charset,'UTF8');
[ where rimdb_atitles has an index on column "attribs varchar[]" ]
Uh-huh. Actu
cassert was on. Now debug is on, too.
I updated from cvs-head just now.
configure knows it is a linux box.
Should it be trying to link to libwsock32.so
or not? If this is a legitimate link, then
the problem is different than if it is trying
to link it in erroneously.
--elein
The is the top of
On Tue, 12 Aug 2003, Andrew Dunstan wrote:
>
> (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 so
Hannu Krosing <[EMAIL PROTECTED]> writes:
> A question to the core - are there any plans to rectify this for less
> fortunate languages/charsets?
I'm not planning to fix it personally, if that's what you mean. I agree
somebody should do something about it. Possibly the C99
routines can be used
Gavin Sherry <[EMAIL PROTECTED]> writes:
> On Tue, 12 Aug 2003, 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?
> Can you give an example of this usage of this API? I am wondering whether
>
On Sun, Aug 10, 2003 at 09:36:58PM -0700, Vadim Mikheev wrote:
> Thanks to everyone!
And thanks to you. I can say for sure that if it weren't for your
work, we'da been sunk. Thanks so much.
> Good luck on your ways.
And on yours. All best.
A
--
Andrew Sullivan
Alvaro Herrera Munoz <[EMAIL PROTECTED]> writes:
> What about the use of a shared sequence object to generate sysids?
I didn't think it needed its own mention in the TODO item, but if you
want to...
regards, tom lane
---(end of broadcast)--
Thanks. Added.
---
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 som
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 slower
> than other databases I ran it on. He
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 pager? Are you manually starting
Rod Taylor <[EMAIL PROTECTED]> writes:
> Do you happen to have any numbers comparing prepared inserts in a single
> transaction against copy?
COPY is about a factor of 6 faster, it appears. I got 11.8 versus
1.87 seconds for loading the same amount of data (with the 3-column
test table). So COPY
1 - 100 of 353 matches
Mail list logo
