On Wed, 2006-04-05 at 14:46 +0200, Stefan Nobis wrote:
Is there any way (or working solution) to extend PostgreSQL to accept
Oracles outer join syntax with '(+)'?
Not AFAIK, and there are no plans to add support that I'm aware of.
EnterpriseDB claim to have pretty good Oracle compatibility, so
On Tue, 2006-03-21 at 16:58 -0500, Kevin Murphy wrote:
I have a table for which PG 8.3 is guessing wrong about a plan when the
result set gets large.
There is no such thing as PG 8.3.
- Index Scan Backward using merged_weight_date_idx on merged
(cost=0.00..31295593.98 rows=141839
On Sun, 2006-03-05 at 08:50 +0530, IYENGAR SURESH PARTHASARATHY wrote:
i want to fully understand the functioning of postgres indexes with
respect to the code.
See src/backend/access/ in the source tree, specifically the nbtree/,
hash/, gist/ and index/ subdirectories -- each directory has a
On Thu, 2006-02-23 at 17:12 -0300, Carlos Henrique Reimer wrote:
When the pg_locks view is used the internal lock manager data
structures are momentarily locked and that is why I would like to know
if some application is reading the pg_locks view and how many times.
Is there a way to
On Sun, 2006-02-26 at 12:08 -0500, Tom Lane wrote:
We'd consider removing these features if they were actually blocking
support of some spec-required behavior ... but since they don't, it's
quite unlikely they'll ever be removed.
Right; there are plenty of places in which PostgreSQL extends
On Fri, 2006-02-17 at 11:34 +0800, Qingqing Zhou wrote:
AFAIK there is no such API for this purpose. The reason is that to access
BTree, you have to setup complex enough environment to enable so. For
example, the buffer pool support, the WAL support etc. So though exporting
such API is easy to
On Fri, 2006-01-20 at 09:16 +0100, DB Subscriptions wrote:
BEGIN
CREATE USER NEW.userid WITH PASSWORD NEW.pword IN GROUP NEW.groupe;
RETURN new;
END;
You can't use PL/PgSQL variables in DDL commands. Try using EXECUTE:
EXECUTE 'CREATE USER ' || NEW.userid || '...';
-Neil
On Tue, 2006-01-17 at 15:01 -0800, Glen Parker wrote:
We're still on 7.4 (sorry, probly should have mentioned that). Does
that documentation apply to the 7.4 series as well?
AFAIK, there haven't been any major changes to TOAST since 7.4, so most
of that documentation should be applicable.
On Sun, 2006-01-08 at 00:12 +, Marcos José Setim wrote:
I'd like that create functions in plpgsql with prepared SQL and plan
saved, to that the Postgresl increase the performance of executions.
This is possible?
plpgsql internally caches query plans the first time a function is
invoked
On Sat, 2006-01-07 at 20:38 +, Marcos José Setim wrote:
I want to use the Prepare and Execute resources of PostgreSQL to
increment the performance of my SQL's.
$sSQL = 'INSERT INTO teste (nome) VALUES( ? )';
$oDB-Prepare( $sSQL );
The PREPARE documentation states:[1]
Prepared
[EMAIL PROTECTED] wrote:
PostgreSQL runs for a while but always eventually (30min - 2hrs) crashes.
Dec 20 17:14:57 server4 kernel: postmaster: page allocation failure.
order:0, mode:0xd0
Dec 20 17:14:57 server4 kernel: [c0143271] __alloc_pages+0x2e1/0x2f7
This looks like a kernel or
On Fri, 2005-11-18 at 11:00 +0100, Wolfgang Keller wrote:
Given the focus of Sun on fault-tolerance etc., one of THE projects
that they should definitely sponsor is
http://gborg.postgresql.org/project/pgreplication/projdisplay.php
AFAIK pgreplication is no longer active. However, the Slony
On Sun, 2005-23-10 at 16:35 -0700, Steve V wrote:
Which library is GetTopTransactionId() available in?
It's defined in the backend executable, as is GetCurrentTransactionId().
A similar wrapper function to the one shown here:
http://archives.postgresql.org/pgsql-general/2005-06/msg00709.php
On Tue, 2005-18-10 at 22:21 -0500, Tony Caduto wrote:
From what i understand Postgresql will scale with more cpus, but not in
the same way as threaded server would.
Threading isn't really relevant. PostgreSQL currently forks a new
process for each client connection, and each process can be
On Mon, 2005-17-10 at 12:25 -0500, Jim C. Nasby wrote:
So, if you have a bunch of int2's all next to each other in a table,
they will happily just consume 2 bytes. The issue comes when you try
and mix them with other fields randomly, since many other fields
require int alignment.
We could
On Sat, 2005-15-10 at 16:42 -0400, jeff sacksteder wrote:
It occurs to me that I don't know how to define unsigned integer
datatypes. I'm making a schema to describe network packets and I need
columns to contain values from 0-255, etc.
I can't seem to find any documentation on this. What's
On Fri, 2005-14-10 at 09:43 -0400, John D. Burger wrote:
I believe these queries are exactly equivalent, but I presume the
planner doesn't know that.
explain select gazPlaceID from gazPlaces
where gazPlaceID not in (select gazPlaceID from gazContainers);
explain select gazPlaceID
On Tue, 2005-11-10 at 14:43 +0200, Martijn van Oosterhout wrote:
My personal favourite bug-tracker is debbugs, as used by the Debian
Project. You can submit bugs by email, they get forwarded to
maintainers (which can be a mailing list) via email. When they reply,
the reply is also stored with
On Thu, 2005-06-10 at 12:07 -0600, Aly S.P Dharshi wrote:
http://sql-info.de/postgresql/postgres-gotchas.html
Any comments from folks on the list ?
SELECT column alias, ...: this is a known issue. AFAIK it is not easy
to solve.
Unquoted object names fold to lower case: this is intentional,
Kevin Murphy wrote:
I just wanted to confirm that the COPY command always stores data in the
table in the order in which it appears in the import file.
This is not the case -- depending on the content of the FSM, the newly
added rows might be distributed throughout the table.
-Neil
Emi Lu wrote:
Greetings,
If one column col1 is defined as :
col1 varchar(1) not null default ''
Does it means that col1's definition is equal to
col1 char(1) not null default ''
Not quite; for example,
neilc=# create table t1 (x char(1) not null);
CREATE TABLE
neilc=# create table t2 (x
Alvaro Herrera wrote:
IIRC Neil Conway posted a patch to make 8.0.2 use LRU instead of ARC,
when the whole patent issue arised.
http://archives.postgresql.org/pgsql-patches/2005-01/msg00253.php
-Neil
---(end of broadcast)---
TIP 9: In versions
Tom Lane wrote:
Joseph Shraibman jks@selectacast.net writes:
If I put the pg_xlog directory on its own disk, then that disk fails,
does that mean the postgres is hosed or does it just mean that postgres
no longer safe from a power outage?
The latter. The WAL is actually write-only during
[EMAIL PROTECTED] wrote:
Does Postgres have any kind of configuration that determines the
speed of data transfer to the clients?
No.
Is there any kind of connection priority?
No, although it is possible to crudely set priorities via OS-level tools
like nice(1).
-Neil
Scott Marlowe wrote:
You might want to schedule analyzes to run every thirty minutes or every
hour.
I doubt that is necessary or wise. Rerunning ANALYZE should only be
necessary when the distribution of your data changes significantly --
e.g. after a bulk load or deletion of a lot of
Joshua D. Drake wrote:
If you are using savepoints you can rollback to a specific point of
a parent transaction.
Although you can't use savepoints (explicitly) in functions. PL/PgSQL
exceptions (which are actually implemented internally via savepoints)
can be used to achieve a similar
Alvaro Herrera wrote:
I don't think you can use just plpgsql's parser. The problem is that it
relies on the main backend parser to figure out anything it doesn't
understand.
I think it depends on what kind of information you want to extract from
a PL/PgSQL function definition. The PL/PgSQL
Vivek Khera wrote:
The first sentence rules out MySQL, so the second sentence should read
So that leaves Postgres. Your problem is solved ;-)
(If you are accustomed to Oracle, you are probably expecting an ACID
database, which rules out MySQL too).
Does MySQL with InnoDB not qualify as
laser wrote:
SELECT url,sum(ct) as ctperkw from ctrraw group by url order by ctperkw
desc limit 1000;
and the query run out of memory, the log file attached.
Have you run ANALYZE recently? You might be running into the well-known
problem that hashed aggregation can consume an arbitrary amount
[EMAIL PROTECTED] wrote:
Is there a similar command in Postgresql so that the client application
can find out if there's an unresolved transaction before it starts a new
one?
See PQtransactionStatus() in libpq; if you're using a different language
interface, it should provide some means to
Tino Wildenhain wrote:
Google or your favourite search engine helps :-)
http://www.postgresql.org/files/documentation/books/aw_pgsql/node71.html
is among the first results.
Unfortunately those docs are quite out of date. This page is better:
Dinesh Pandey wrote:
./configure --enable-integer-datetimes --prefix=/usr/local/pgsql
--with-tclconfig=/usr/local/lib --with-tcl
configure: error:
*** Could not execute a simple test program. This may be a problem
*** related to locating shared libraries. Check the file 'config.log'
*** for
Alvaro Herrera wrote:
No, we don't have SQLERRM support yet. If you were asking about getting
the messages from RAISE EXCEPTION, I'm afraid there's no way to get it
in the EXCEPTION clause.
If you want to contribute it, patches are welcome ...
Actually, Pavel Stehule sent in a patch for this
Alvaro Herrera wrote:
Huh, I meant a patch for getting the error message from RAISE EXCEPTION.
Does Pavel's patch address that too?
Yes.
(I just posted a revised patch to -patches, I'll apply it later tonight.)
-Neil
---(end of broadcast)---
Mohan, Ross wrote:
1) Many (many!) uninitialized variables in code. Optimizers don't
do well with this.
Um, what?
2) Not clear (to me, a nonprogrammer) whether this is GNU C, ANSI C,
Postgres C, or what the overall coding protocol is.
Postgres is mostly ANSI C89, with limited use
On Wed, 2005-06-01 at 08:22 +0200, Philippe Lang wrote:
What is the best way to calculate an MD5 Sum for a set of rows in a
table, on a Postgresql server?
The md5() builtin function. contrib/pgcrypto is available if you need
more sophisticated hashing / encryption.
-Neil
On Tue, 2005-05-31 at 15:43 -0400, Tom Lane wrote:
OK, next question: is this a bug fix we should back-patch into 7.4,
or just change it in HEAD?
I agree with Alvaro: fix it in HEAD, but don't backport the change to
8.0 or 7.4.
-Neil
---(end of
Himanshu Baweja wrote:
is there any other better way by which i can get a list of locks
acquired and waited for during entire run of my application
Hacking the backend would be the easiest route, I think. Why do you need
this information -- what are you trying to do?
-Neil
Felix E. Klee wrote:
I have the created a C-Language function (code is below). Now, I
wonder: How do I handle exceptions, for example if malloc cannot assign
the necessary memory? Do palloc and pfree handle such a case
cleanly?
Yes -- they will roll back the current transaction on if there
Paul Newman wrote:
We are currently using a 32byte varchar for our primary keys. We tried
to reduce this down to 16 bytes but varchar didn't seem to store this
correctly.
In what way was it not stored correctly? The size limit should not
significantly affect varchar behavior, other than bounding
Dan Black wrote:
How can i calculate table and index size on hard disk?
See contrib/dbsize in the PostgreSQL source tarball.
-Neil
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Tom Lane wrote:
Performance?
I'll run some benchmarks tomorrow, as it's rather late in my time zone.
If anyone wants to post some benchmark results, they are welcome to.
I disagree completely with the idea of forcing this behavior for all
datatypes. It could only be sensible for fairly wide
Marc G. Fournier wrote:
Please note that the security issues were those already reported by Tom
Lane, as well as a manual fix for them. These releases are mainly to
ensure that those installing and/or upgrading existing installations
have those fixes automatically.
Note that if you're
Bruce Momjian wrote:
Is there a TODO anywhere in this discussion? If so, please let me know.
There are a couple:
- consider changing hash indexes to keep the entries in a hash bucket
sorted, to allow a binary search rather than a linear scan
- consider changing hash indexes to store each key's
Ying Lu wrote:
May I know for simple = operation query, for Hash index vs. B-tree
index, which can provide better performance please?
I don't think we've found a case in which the hash index code
outperforms B+-tree indexes, even for =. The hash index code also has
a number of additional
Christopher Petrilli wrote:
This being the case, is there ever ANY reason for someone to use it?
Well, someone might fix it up at some point in the future. I don't think
there's anything fundamentally wrong with hash indexes, it is just that
the current implementation is a bit lacking.
If not,
Jim C. Nasby wrote:
Having indexes that people shouldn't be using does add confusion for
users, and presents the opportunity for foot-shooting.
Emitting a warning/notice on hash-index creation is something I've
suggested in the past -- that would be fine with me.
Even if there is some kind of
Jim C. Nasby wrote:
No, hash joins and hash indexes are unrelated.
I know they are now, but does that have to be the case?
I mean, the algorithms are fundamentally unrelated. They share a bit of
code such as the hash functions themselves, but they are really solving
two different problems (disk
Tom Lane wrote:
On the other hand, once you reach the target index page, a hash index
has no better method than linear scan through all the page's index
entries to find the actually wanted key(s)
I wonder if it would be possible to store the keys in a hash bucket in
sorted order, provided that
Tom Lane wrote:
I have a gut reaction against that: it makes hash indexes fundamentally
subservient to btrees.
I wouldn't say subservient -- if there is no ordering defined for the
index key, we just do a linear scan.
However: what about storing the things in hashcode order? Ordering uint32s
Vlad wrote:
ok, since there is no gurantee that server-side prepared query is
still active, pergaps postgresql interface library provide way to
check if a prepared before query still alive prior runing exec
I'm not sure I quite follow you -- in some future version of the backend
in which prepared
Tom Lane wrote:
That's what it is supposed to do. It would hardly be possible to
prepare a query at all if we had to wait till EXECUTE to find out
which tables it was supposed to use.
An alternative would be to flush dependent plans when the schema search
path is changed. In effect this would
Dennis Sacks wrote:
The disadvantage is, you'll have to have some process for deleting
old data from the table, as it will stay around and it will bite you
when you get the same pg_backend_pid() again down the road.
Rather than use pg_backend_id(), why not just assign session IDs from a
sequence?
Hubert Fröhlich wrote:
Those days, we had PostgreSQL 7.1 and 7.2, and we had to be careful oids
approaching 2^32 (2.14 billion)
Now, we have 8.0. What does the situation look like?
With the default settings, there is exactly the same risk of OID
wraparound as in earlier releases. However, you
Pavel Stehule wrote:
CREATE OR REPLACE FUNCTION foo(integer, integer) RETURNS integer AS $$
BEGIN
RETURN $1 + $2;
END; $$ LANGUAGE plpgsql;
CREATE OR REPLACE FUNCTION foo(integer) RETURNS integer AS $$
BEGIN
RETURN foo($1,10); -- 10 is default value
END; $$ LANGUAGE plpgsql;
Note that if you
Dawid Kuroczko wrote:
For a test you might want to try also this approach (both from perl and
from psql):
$dbh-do('PREPARE sth_tim (int,inet,boolean,timestamptz) AS INSERT
INTO timestamps VALUES ($1,$2,$3,$4)');
$sth_tim = $dbh-prepare(EXECUTE sth_tim(?,?,?,?));
...and later execute it. (and
Chris Smith wrote:
I'm trying to use a limit clause with delete, but it doesn't work at the
moment
It isn't in the SQL standard, and it would have undefined behavior: the
sort order of a result set without ORDER BY is unspecified, so you would
have no way to predict which rows DELETE would
Chandra Sekhar Surapaneni wrote:
Can we write our own niladic functions in 8.0.0? I want to write a
niladic function similar to current_timestamp, but I did not find any
information in the documentation.
If you mean a function without any arguments, it is trivial:
CREATE FUNCTION foo() RETURNS
Edwin New wrote:
I have encountered a situation where a java process is dying but leaving
locks active.
If the connection to PostgreSQL is severed (e.g. the client actually
disconnects), the current transaction will be rolled back and any held
locks will be released.
So it seems that the
Stanislaw Tristan wrote:
It's a possible to compress traffic between server and client while server
returns query result?
It's a very actually for dial-up users.
What is solution?
You could use an SSH tunnel with compression to achieve this.
-Neil
---(end of
Bruce Momjian wrote:
Syntax error reporting has been improved in our code so 8.1 might be
better and catching such errors.
Yes, current sources catches this at definition-time:
% psql -f test.sql
psql:test.sql:21: ERROR: syntax error at or near EXCEPTIONRATIO_OUT
at character 1
QUERY:
On Tue, 2005-02-15 at 20:13 -0700, Michael Fuhr wrote:
Do user-defined functions need to check palloc()'s return value,
or does return guarantee success?
It guarantees success.
-Neil
---(end of broadcast)---
TIP 9: the planner will ignore your
On Tue, 2005-02-08 at 18:11 -0500, Tom Lane wrote:
Vitaly Belman [EMAIL PROTECTED] writes:
Doing an EXECUTE for a query which returns results still yields 'f'
for the FOUND variable.
This is not a bug. Read the list of statements that update FOUND.
EXECUTE is not one of them.
See also
On Wed, 2005-02-09 at 10:48 +0530, Antony Paul wrote:
Hi all,
This is giving error in 7.3.3.
CREATE TEMP TABLE temptest3(col int PRIMARY KEY) ON COMMIT DELETE ROWS;
ERROR: parser: parse error at or near ON at character 51
Is this supported.
No. Looking at the manual would have made
Paul Tillotson wrote:
Does anyone know a safe way to shutdown just one backend
Sending it a SIGTERM via kill(1) should be safe.
-Neil
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
On Tue, 2005-02-01 at 01:53 -0500, Tom Lane wrote:
/*
* Increment command counter between queries, but not after the
* last one.
*/
if (planlist_item != NULL)
CommandCounterIncrement();
but planlist_item will *never* be NULL here.
On Tue, 2005-02-01 at 18:37 -0500, Tom Lane wrote:
Do you think it's worth groveling through the other uses of forboth()
for the same type of error?
I just checked the other uses of forboth(), and didn't notice any
errors.
-Neil
---(end of
Josh Berkus wrote:
If you know of a PostgreSQL package, from any source, that installs with trust
on network ports, please notify Core (and Core only, please).
Why only -core?
-Neil
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Jim C. Nasby wrote:
I'd really like to see an improvement in how sort_mem/work_mem is
handled.
So would I :) (I think it's well known that the current system is not
optimal.)
Do you have any thoughts on how to improve it?
-Neil
---(end of
Tom Lane wrote:
The correct place for a sysadmin to limit memory usage would be in the
ulimit settings the postmaster starts under. Of course, Neil's argument
still holds in general: anyone who can write arbitrary queries is not
going to have any difficulty in soaking up unreasonable amounts of
On Thu, 2005-01-27 at 20:03 -0600, Jim C. Nasby wrote:
Yes, there is a risk allowing ad-hoc settings; you can starve the
machine for memory.
A malicious user who can execute SELECT queries can already consume an
arbitrary amount of memory -- say, by disabling GEQO and self-joining
pg_class to
On Mon, 2005-01-24 at 21:03 -0600, Wes wrote:
Implicit indexes created by a constraint do not appear to honor the default
tablespace. The index gets created in the null tablespace.
I took pg_dumpall output and modified the schema to place everything in
specific table spaces. When the
Richard Huxton wrote:
You want elsif - plpgsql isn't a hugely sophisticated language and its
parser is having trouble there. I'm guessing the parser is somehow
putting the elseif branch under the initial then so it never gets
executed.
Indeed; the parser thinks an unrecognized keyword indicates
On Thu, 2004-12-16 at 11:09 -0500, Tom Lane wrote:
I think we should go ahead and do that for 8.0. I'm getting tired of
reading reports that stem from this mistake (I think this is the third
one in the past month ...). I can't see any real downside to accepting
both spellings, can you?
I
Eric Brown wrote:
I've got quite a few plpgsql functions that insert, update or delete.
They're all declared to return void. All other functions, I can just run
'select f(...);' from psql to test them. I don't understand how to test
these ones that return void from psql.
neilc=# create function
On Mon, 2004-12-13 at 17:43 -0500, Jimmie H. Apsey wrote:
Hello all,
I have just loaded Postgresql 7.3.6-7 onto a new server on the
recommendation of Tom Lane. It is part of Red Hat AS 3.
I have Postgresql 7.1.3-5 running on Red Hat AS 2.1.
I have a simple view from which I select on both
On Wed, 2004-12-15 at 10:22 +1100, Harvey, Allan AC wrote:
I have a small table about 20 rows, a constant, that is receiving
about 160 updates per second.
The table is used to share gathered data to other process asynchronously.
After 5 min it is 12 updates per second.
Performance returns
On Tue, 2004-12-14 at 14:12 -0600, Scott Marlowe wrote:
IS this same issue true for hash or GiST indexes?
Yes, it is: currently, only btree indexes are WAL safe.
(I spent some time recently looking into adding page-level concurrency
and WAL to GiST, but I haven't had a chance to finish that
On Tue, 2004-12-14 at 17:15 -0800, Tim Vadnais wrote:
My question is:
What is stand-alone mode?
http://www.postgresql.org/docs/7.4/static/app-postgres.html
-Neil
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Sun, 2004-12-12 at 20:25 -0800, Lonni J Friedman wrote:
OK, thanks. So is there any real benefit in doing this in a generic
(non-dspam) sense, or is it just a hack that wouldn't be noticable?
Any risks or potential problems down the line?
It saves 4 bytes per row; depending on alignment
On Mon, 2004-12-06 at 19:37 -0500, Paul Tillotson wrote:
I seem to remember hearing that the memory limit on certain operations,
such as sorts, is not enforced (may the hackers correct me if I am
wrong); rather, the planner estimates how much a sort might take by
looking at the statistics
On Mon, 2004-12-06 at 22:19 -0300, Alvaro Herrera wrote:
AFAIK this is indeed the case with hashed aggregation, which uses the
sort_mem (work_mem) parameter to control its operation, but for which it
is not a hard limit.
Hmmm -- I knew we didn't implement disk-spilling for hashed aggregation,
On Mon, 2004-12-06 at 23:55 -0500, Tom Lane wrote:
Bear in mind that the price of honoring sort_mem carefully is
considerably far from zero.
I'll do some thinking about disk-based spilling for hashed aggregation
for 8.1
The issue with the hash code is that it sets size parameters on the
On Tue, 2004-11-30 at 17:54 +1100, Johan Wehtje wrote:
I am getting the error Column n.nsptablespace does not exist in my
application when I connect using my Administrative tool. This only
happens with Version 8, but it does crash my application, does anyone
have any ideas ?
You need to
On Thu, 2004-11-25 at 10:24 +0100, Bjørn T Johansen wrote:
do I still need to use ::int8 to
make it use indexes in 8.0 as I need in 7.x?
That should no longer be necessary.
-Neil
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
On Thu, 2004-11-25 at 15:00 -0500, Fred Fung wrote:
I am running PostgreSQL 7.4.5 and I notice the following 2 sets of
error messages generated by the postmaster everything I do a query
through my frontend application program
The source of the errors is your frontend application, not
Ulrich Meis wrote:
CREATE TABLE data.question_result (
id bigserial PRIMARY KEY,
trial_idbigint NOT NULL REFERENCES data.trial(id),
question_id bigint REFERENCES content.question(id),
two more columns,
);
mydb=# explain analyze select *
On Mon, 2004-11-22 at 08:59 -0500, Geoffrey wrote:
So that would say the previous statements are not accurate? That is,
there's no problem with using a varchar?
Right; there is no reason to prefer CHAR(n) over VARCHAR(n), unless you
need whitespace padding.
-Neil
Peter Eisentraut wrote:
There are certainly ways to handle this. But no one has seriously proposed
getting rid of OIDs and presented a plan for fixing all the other holes that
move would leave.
Right; I certainly have no intention of trying to remove OIDs any time
soon. However, I _will_ be
On Thu, 2004-11-11 at 14:34 -0500, Tom Lane wrote:
Geoffrey [EMAIL PROTECTED] writes:
Do I get more oids on a 64 bit machine?
No.
Nor will OIDs ever be 64 bit, I'd hazard to guess.
In any case using OIDs in applications is a bad idea -- you probably
should not be using them at all, let
Andrew Lazarus wrote:
Is there some clear reason why I can't using EXECUTE of a PREPAREd query
as I can a SELECT statement in CREATE TABLE AS, INSERT, FROM clause,
sub-selects, etc.? If not, wouldn't this be a very useful change?
You can already do CREATE TABLE AS ... EXECUTE.
I agree being able
I don't see the big difference between what Marco is suggesting and user
threads -- or to be more precise, I think user threads and event-based
programming are just two sides of the same coin. A user thread just
represents the state of a computation -- say, a register context and
some stack.
Henk Ernst Blok wrote:
I assume(d) the more expensive statistics (e.g., value distribution
info) are updated only when outdated too much or on request (manual
vacuum).
They are only updated on request -- i.e. when an ANALYZE is issued.
So if explain can get the most recent count, why
not use
On Mon, 2004-10-25 at 22:59, Deepa K wrote:
Hi,
I am using postgresql 7.1.3 in RedHatLinux 7.2.
Note that PostgreSQL 7.1.3 is quite old -- you should consider
upgrading.
Can anyone tell me how
to connect with postmaster through TCP socket (it is started with -i
option) using libpq from an
Marc G. Fournier wrote:
In order to address a recent security report from iDefence, we have
released 3 new point releases: 7.2.6, 7.3.8 and 7.4.6
Assuming you're referring to the make_oidjoins_check bug, I don't think
it is accurate to bill these as security releases. As the 7.4.6
release notes
On Mon, 2004-10-25 at 00:43, Tom Lane wrote:
He's not. There were two other recent security reports, which core kept
to ourselves until the release could be made.
Ah, ok -- fair enough. Are those additional security fixes mentioned in
the release notes?
-Neil
On Thu, 2004-10-21 at 06:40, Thomas F.O'Connell wrote:
Is the ON COMMIT syntax available to temporary tables created using the
CREATE TABLE AS syntax?
No, but it should be. There's a good chance this will be in 8.1
If not, is there a way to drop such a table at
the end of a transaction?
On Mon, 2004-10-18 at 14:49, Ed L. wrote:
I *think* I'm seeing vacuum analyze queries launched automatically on an
8.0.0beta3 (unless I have a rogue autovac running that I haven't spotted).
Is this something new in 8.0 and to be expected?
No.
#vacuum_cost_delay = 0# 0-1000
On Wed, 2004-10-13 at 06:31, Ed Stoner wrote:
I am unable to use the CREATE USER command with numeric user names
(i.e. CREATE USER 35236 WITH PASSWORD '1234';). Is this a limitation or
a problem somewhere with how I have things configured? Is there are
workaround?
A username is an
On Wed, 2004-10-13 at 14:58, John Ossmann wrote:
I'm not sure where to find it exactly, but does anyone know how much
data a column of type text in a postgres DB can hold?
There is no limit on what text itself can contain. However, a field of
any data type can contain at most 1GB (compressed --
1 - 100 of 150 matches
Mail list logo
