PQconnectdb().
BTW this all assumes that you have a thread-safe libc; if malloc is
not thread-safe then all bets are off...
Is there anyone working on multi threading for libpq ?
I don't really see a need for libpq to be thread-aware.
regards, tom lane
ames in this context...
regards, tom lane
2.2.8.
I still see it with 6.5-current sources. Will take a look.
regards, tom lane
Lauri Posti [EMAIL PROTECTED] writes:
I've been trying to get postgres LO interface to work with python.
I think you need begin/end transaction around lo_open ... lo_close
sequence.
regards, tom lane
date performance?
No, it would not help a query like that --- though if you added a clause
like "where divis = 'oldvalue'" then an index would help to find the
rows that need updated. Actually, every index you add *slows down*
updates, since all the indexes must be updated along with the table.
regards, tom lane
if the serial column
was created "by hand" with a "DEFAULT nextval('some_sequence')" clause?
I suspect that any way we jump on this sort of question will be wrong
for some apps, so it should be possible to suppress system copying of
attributes...
regards, tom lane
be willing to send me a database dump so that I can
reproduce the problem exactly? (If the dump is no more than a few
megabytes, emailing it should be OK.) No big hurry, since I probably
won't be able to get to it for a week or so anyway.
regards, tom lane
seconds with epoch 1/1/2000), so relying on the internal representation
of abstime would be a bad idea...
regards, tom lane
ks to find the patch.
regards, tom lane
ql, rather than those of the Postgres server, which is usually
a Good Thing. Also, if you are contacting a server on a different
machine, \copy works with files in the local filesystem, not the
server's filesystem.
regards, tom lane
t.
I see no way that allowing the transaction to commit after an overflow
can be called consistent with the spec.
regards, tom lane
See the difference? 120 vs 144? What's causing that I wonder...
and would it explain the failure to reattach?
regards, tom lane
Is this in 7.0 ?
Looks like it's called just plain "substr" now. See
http://www.postgresql.org/docs/postgres/functions.htm
regards, tom lane
this in Red Hat 6.0
Weird. Do you not have 'tr' in your PATH? You wouldn't be running with
some bizarre LOCALE setting, by any chance?
regards, tom lane
unmatched entries...
Certainly 70 rows are not going to strain memory ;-). My guess is that
the query didn't do what you thought, but instead produced some sort
of cross-product result...
regards, tom lane
or mis-extracted) here. So it kinda looks to me like we could rip out
this test, hardwire the translation as
tr '[a-z]' '[A-Z]'
and be no worse off. Does anyone recall why this test is in there to
begin with?
regards, tom lane
guess this is another
one ...
If you really don't want to update your app's code just yet, you can
install a pg_proc entry that defines textpos() with a CREATE FUNCTION
command. But the long-term answer is to fix your code to conform with
the standard.
regards, tom lane
pg_upgrade to update from any 6.5-or-later version if you
are feeling adventurous, but I'd definitely suggest making a backup
first in case things go wrong and you have to initdb and restore.
regards, tom lane
Peter Eisentraut [EMAIL PROTECTED] writes:
On Tue, 9 May 2000, Tom Lane wrote:
dnl Check tr flags to convert from lower to upper case
Does anyone recall why this test is in there to begin with?
I don't see the results of this test being used anywhere at all, so I'd
say yank it. If your
-by-reference datatypes. There are plans on the table to fix that
for 7.1.
But, that might or might not be your problem. It's difficult to give
any advice without some details about the queries that are giving you
trouble.
regards, tom lane
m catalogs for subreleases. Sorry.
Just counting entries, that may not be the only type that has
entries in pg_amop but not pg_amproc. I feel another oprsanity
regression-test check coming on...
regards, tom lane
ds.
Could be that 7.0 is less willing to use the index than 6.5 was. See
thread "indexes ingnored on simple query in 7.0" over in pgsql-sql for
ways to investigate the problem and one possible solution.
regards, tom lane
the trouble.
regards, tom lane
stified. As it happened
they would pick an indexscan for the one-sided-inequality case even
with no stats available. In some cases that was good, in others
it'd lose big.
regards, tom lane
if initdb
didn't overwrite it (nor delete it on failure), but I'm not sure it's
worth the trouble.
Something that would be a lot simpler is to refuse to run at all
if the $PGDATA dir exists and is nonempty ;-)
regards, tom lane
configure script asks
you if you want a shared libperl. You can probably default all the
other answers, except maybe for the location you want the perl directory
tree placed ...
regards, tom lane
PS: be careful not to lose any Perl modules you may have installed
that
regards, tom lane
d recreate the function.
I believe there is a "LOAD" command that will reload the library without
needing to restart the backend. Not sure if that's any easier than
just restarting though...
but this should probably be noted somewhere in
the programmers manual.
Agreed.
.
regards, tom lane
: arguments required
regards, tom lane
referencing a function whenever you remake
the function.
regards, tom lane
be a lot of code involved, we just need a
well-thought-out spec for how it should work. Comments anyone?
regards, tom lane
y particular users any access to particular databases, but
that's about the extent of your flexibility. This is being worked on...
- What do I need to do in order to allow multiple users the abililty to
create tables in a single database?
Nada, see above.
regards, tom lane
bad record and then reload
it.
Slightly faster than a dump and reload:
RENAME broken table to something else;
CREATE TABLE new-table;
INSERT INTO new-table SELECT * FROM broken-table WHERE custid IS NOT NULL;
then recreate the indexes wanted on new-table...
regards, tom lane
the error message
then it looks like your path may be messed up...
regards, tom lane
,
but maybe there's a screw loose somewhere...
regards, tom lane
about how the queries are being executed?
Do you by any chance have the 6.5.3 system still available to compare
its EXPLAIN output?
regards, tom lane
directory and
rename the file. I have tested this with version 7.0.
Boo hiss --- the physical file rename must be the *last* step in
table rename, after all other possible errors have been checked.
Evidently it's not :-(. Will fix.
regards, tom lane
underneath. Will look.
regards, tom lane
ahead is
needed to tell which production to use next. You might care to read
the 'bison' (GNU yacc) manual on the subject of removing parse
conflicts.
regards, tom lane
should eliminate those problems.
regards, tom lane
n and sort the report
gets no data for the first 30 minutes and then runs at about 4 times the
rate of the index scan.
Right, that's what you'd expect: the sort has to be completed before it
knows which row to deliver first, but an indexscan has no such startup
cost.
regards, tom lane
.
regards, tom lane
run them via a cursor or a plain SELECT.
regards, tom lane
reference counts. But the real question is how did it get
into this state in the first place...
regards, tom lane
$PGDATA"`
if test "x$CONTENTS" = x
Are we talking 7.0.1 material, btw?
Well, we would be if we were sure of the patch. I'm a little worried
about portability though. Given that this isn't a very critical issue
(IMHO) I'd recommend saving it for the 7.1 cycle.
regards, tom lane
Barry Lind [EMAIL PROTECTED] writes:
I am curious, how does PostgreSQL support tables larger than 2Gig, given
the file per table architecture?
Multiple files per table ...
regards, tom lane
.
regards, tom lane
nyone much noticing...
regards, tom lane
ecommended in our FAQ, I believe.
(Hey Bruce, does your new book go into this stuff?)
regards, tom lane
ppropriate patch is
#ifndef NO_FASTPATH
+ isNull = false;
retval = fmgr_array_args(fid, nargs, arg, isNull);
#else
retval = NULL;
#endif /* NO_FASTPATH */
regards, tom lane
backward-compatibility reasons...
regards, tom lane
we are doing anyone a service if we tweak initdb in a way
that will make it slightly safer to keep random files in PGDATA. You
shouldn't do it anyway, and modifying initdb to make it look like you
can will only increase the risk of people accidentally screwing up their
installation.
regards, tom lane
obviously going to be a necessary feature
if we want to make the existing flavor of large objects obsolete. There
have been some preliminary discussions about it --- AFAIR no one's laid
out a complete proposal yet.
regards, tom lane
se Windoze as a
platform for a mission-critical application, regardless of database
engine choice. So the cygwin port is pretty much a toy IMHO.
If MySQL wants to have the toy-application market segment, they're
welcome to it.
regards, tom lane
,
but you can find it if you search by module name.
regards, tom lane
pretty silly that CREATE USER is stiffnecked about this
when DROP TABLE is not --- the bad consequences of rolling back DROP
TABLE are a lot worse.
regards, tom lane
se queries.
Perhaps someday we will try to convert simple uses of MIN/MAX into
queries like these, but for now, you gotta do it by hand.
regards, tom lane
with
WHERE DOB = '1999-01-01'
regards, tom lane
one table is better than restoring your whole DB.
In the meantime, this is a high-priority bug fix...
regards, tom lane
so I wouldn't advise doing it during normal usage of the
system.)
regards, tom lane
pical uses...
regards, tom lane
?
regards, tom lane
exit status
You probably need an explicit "-lcrypt" in your link command. Some
platforms need that, some don't...
regards, tom lane
m, at least not IMHO. For now,
the answer is "if it hurts, don't do it ;-)"
regards, tom lane
e the same value you
find in atttypmod for the underlying table's field.
regards, tom lane
s not
exist" and "init_fcache: null probin for procedure 481". This seems
to be due to VACUUM (on system tables) causing syscache entries to be
flushed at unexpected times. I've committed patches for the two cases
I observed, but there may be more lurking...
regards, tom lane
Ed Loehr [EMAIL PROTECTED] writes:
Tom Lane wrote:
I can't reproduce any problem with just a "vacuum" (with or without
analyze) and no following command.
I did, however, notice that very occasionally the inserting process
would spit out weird error messages like "Functio
querytree redesign
planned for 7.2.
Thoughts anyone?
regards, tom lane
-
retentive about type checking. Sometimes that's good, sometimes not
so good.
regards, tom lane
ver exceed NAMEDATALEN-1.
regards, tom lane
he double quotes at parse time instead
of run time :-(.
Will fix for 7.1 ... in the meantime, don't name your sequences that way
...
regards, tom lane
to be updated.
Hey Vince, isn't that stuff supposed to be rebuilt from sources
nightly?
regards, tom lane
.)
Also, how many rows in the table?
regards, tom lane
connection
Hmm, that looks like a backend coredump. Did you find a core file in
the database directory? If so, can you get a backtrace from it?
regards, tom lane
of plpgsql;
dunno what exactly. I'd recommend updating to 7.0.2 and then seeing
if the problem persists. If it does we can dig deeper.
regards, tom lane
.
regards, tom lane
e the
ODBC driver's SQL type = Postgres type mapping if there's a
better definition than what we're using...
regards, tom lane
to quote the column name in
order to refer to it.
It would be useful to see the output of
pg_dump -s -t tablename databasename
for this table.
regards, tom lane
GSQL.5432 together with that error ought
to be sufficient clue I would think...
regards, tom lane
hy doesn't PostgreSQL have a SYSDUMMY table or something like it
(the way Oracle or IBM's DB2 have).
Don't need it, since we don't require a FROM clause.
regression=# select upper('Boulevard');
upper
---
BOULEVARD
(1 row)
regards, tom lane
.
regards, tom lane
Bruce Momjian [EMAIL PROTECTED] writes:
Is the INSERT rule re-ordering mentioned a TODO item?
Darn if I know. I threw the thought out for discussion, but didn't
see any comments. I'm not in a hurry to change it, unless there's
consensus that we should.
regards, tom
sure to the
hundreds of bugs we've swatted since 6.5.
regards, tom lane
error message?
On my system errno 32 is EPIPE, but surely read() should never
return EPIPE.
regards, tom lane
k with 7.0.
regards, tom lane
, and the development
snapshot appears someplace else, but I guess Vince hasn't got
round to it yet ...
regards, tom lane
rtainly do at
the price of losing some error detection capability --- ie, if that
really had been a typo as I first thought, the system wouldn't flag it
for you.
Not sure which way is better. Comments anyone?
regards, tom lane
... check with netstat or lsof or something
like that.
regards, tom lane
clause (or whatever it's called in the parse tree) and select
triggers be hacked into the database?
No. If there were, what makes you think that it'd be easier to
security-audit it than a standalone proxy?
regards, tom lane
o" is not a valid integer value. If you want your app to
accept such things, do your own input parsing and filtering.
A database server should not be lax about what it considers valid
data.
regards, tom lane
'# */
regression'# 'sss
regression*# */
regression-#
Notice the pattern of the 'state' markers in the prompts. It seems
to get the reverse case correct though:
regression-# 'foo
regression'# /*bar
regression'# '
regression-#
Over to you, Peter...
regards, tom lane
data format
conversions for you. I envision this as a separate client program,
so it wouldn't take any deep dark backend-programming ability to write
it, just some knowledge about typical file formats and conversions.
Anyone want to take on the project?
regards, tom lane
port is so slow to reload that no sensible person uses it for
big tables anyway ;-)
regards, tom lane
n transaction blocks,
and trying to avoid that. But an occasional SI overrun is normal and
nothing to worry about ... at least not in 7.x.
regards, tom lane
clue about why it's failing.
regards, tom lane
he details, hopefully that would help someone
else avoid the work.
Please do --- I think a lot of people would find it interesting.
regards, tom lane
ted tables.
regards, tom lane
m the psql coredump
(and also from the backend coredump, if there is one ... which seems
likely)?
regards, tom lane
in the sand is not
a good defense mechanism.
regards, tom lane
1 - 100 of 13723 matches
Mail list logo
