?)
Yes, especially if integrated with some full text index scheme.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
WARNING.TXT ;)
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
;
They were taken from a busy system, but i ran the several times showing
about the same result.
Magnus
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Hannu Krosing [EMAIL PROTECTED]
---(end
.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
SQL99 WITH clause to SELECT
* Add SQL99 WITH RECURSIVE to SELECT
---
Hannu Krosing wrote:
On Tue, 2002-12-03 at 09:20, Dennis Bj?rklund wrote:
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
Now convert
On Mon, 2002-12-02 at 23:59, Joe Conway wrote:
I've hacked the spec file from a 7.2.x source RPM to produce a 7.3 source RPM.
I've also created a set of i686 binary RPMs. These are *not* official PGDG
RPMs, and I'm not an RPM expert by any means (so use at your own risk!), but
I've posted
Shridhar Daithankar kirjutas K, 04.12.2002 kell 20:51:
On 4 Dec 2002 at 20:41, Hannu Krosing wrote:
hannu=# update seq set max_value = 99;
ERROR: You can't change sequence relation seq
hannu=# update pg_class set relkind = 'r' where relname = 'seq';
UPDATE 1
hannu=# update seq set
, you would also have to edit the table definition to use a
pre-created sequence. There is no means of specifying a max_value using
SERIAL.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go
SEQUENCE to be transaction safe.
All *val('seqname') functions are transaction-unsafe, i.e. live outside
transactions.
Why would you want alter transaction to be transaction safe ?
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast
just bit-bucket it?
If we do try to preserve it, how should it work?
Why not use \D for long ids ?
Somewhat similar to -? and --help for command line.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through
.
On most european keyboards you alreday have to use AltGr to get to \
so using an extra shift is not too bad ;)
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
user defined tables (say any_table) so that one can get a list of all
tuple ids in all tables by doing a simple
select tableoid,oid from any_table. This will of course not be very
useful for tables with no oids and where there is no index on oid.
--
Hannu Krosing [EMAIL PROTECTED
, but somehow it
feels that for master-slave replication simple log replay would be most
simple and robust solution.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
pg_user.* from pg_user)
as pg_user;
ERROR: Cannot pass result of sub-select or join pg_user to a function
I there a way to:
a) tell PostgreSQL that the funtion can take any row type as an argument
or
b) to cast the result of subquery to a known row type
--
Hannu Krosing [EMAIL PROTECTED
interfaces.
I have CC'ed both python interface authors.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
pointers, even though there seems to be a
layer called storage Manager which should hide the on-disk format
completely.
Can't there just be some BKI process to add new data entries? I had
the same issues with 7.1 and 7.2,
--
Hannu Krosing [EMAIL PROTECTED]
---(end
at each 1000 tuples, so that a full re-scan is not
neccessary ?
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
--
Hannu Krosing [EMAIL PROTECTED
be easier to avoid name clashes.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Tue, 2003-01-14 at 01:39, Christopher Kings-Lynne wrote:
What about querying the information_schema?
Will information_schema be strictly SQL99 or will it also have
PostgreSQL specific views/fields ?
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast
On Tue, 2003-01-14 at 15:47, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Will information_schema be strictly SQL99 or will it also have
PostgreSQL specific views/fields ?
If it's not strictly conformant to the spec, I see no value in it at
all.
I mean that it could have
,
and are on the reference table of the fkey?
I think Tom was trying to tell that the backend code indeed runs this,
but that it should not be that slow.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
releases (also I dont think you can easily
compile C source on a C# compiler) ;/
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
and then access tuple[ptrarray[5]]
next call to get col[75] will start form col[5] and fill up to col[75]
next call to col[76] will start form col[75] and fill up to col[76]
next call to col[60] will just get tuple[ptrarray[60]]
the above description assumes 1-based non-C arrays ;)
--
Hannu
, intdata2, intdata3, vardata4,vardata5)
but it seems to solve the O(N) problem quite nicely (and forces no
storage growth for tuples with fixlen fields in the beginning of tuple)
and we must also account for NULL fields in calculations .
--
Hannu Krosing [EMAIL PROTECTED
Curt Sampson kirjutas N, 23.01.2003 kell 17:42:
If the OS can handle the scheduling (which, last I checked, Linux couldn't,
When did you do your checking ?
(just curious, not to start a flame war ;)
at least not without patches), eight or sixteen
CPUs will be fine.
cjs
--
Hannu Krosing
, but this will be
hidden inside the field storage in the page)
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9
compatability. But yeah, I know that this can introduce problems with
old dumps, and may not be entirely easy to implement.
If you need a no-OID table, and INSERT INTO it.
cjs
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe
there's a variable-width column in the table
--- which means that all columns to its right are not at fixed offsets,
and have to be scanned for separately in each tuple, AFAICS.
Not only varlen columns, but also NULL columns forbid knowing the
offsets beforehand.
--
Hannu Krosing [EMAIL
Hannu Krosing kirjutas N, 23.01.2003 kell 12:11:
make the pointer array incrementally for O(N) performance:
i.e. for tuple with 100 cols, allocate an array of 100 pointers, plus
keep count of how many are actually valid,
Additionally, this should also make repeted determining of NULL fields
archives?
http://archives.postgresql.org
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
do have a
problem with MKS toolkit, which is a commerical purchase. I would like
to avoid reliance on that, though Jan said he needed their bash.
IIRC mingw tools had win-native (cygwin-less) bash at
http://sourceforge.net/projects/mingw/
--
Hannu Krosing [EMAIL PROTECTED
it by bringing my
work to 7.4 and then doing small amounts of work and then bugging the
list about what would be the best ways to continue, repeating it until
it is done ;)
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading
this
conversation is a waste of time.
I assume you realize that U can't kill -9 the plug ;)
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
even Unix to survive that!
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
.
regards, tom lane
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing
is desperate as his
methodologically completely scientific studies ended up showing that
smoking is healthy and not smoking is not ;), so he seems unable to
publish any of his results in any respectable outlet ;(
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast
and a number did that ?
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
/ ) ?
They claim at least utf-8 (I don't remember other multibyte charsets
being mentioned) support and have a BSD-ish license,
http://pcre.sourceforge.net/license.txt .
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe
pcre, that works both on 8-bit and python's
unicode (either 16 or 32 byte chars, depending on compile options))
It has no specific support for raw utf-8 or other variable-width
encodings.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast
Tom Lane kirjutas T, 04.02.2003 kell 21:18:
Hannu Krosing [EMAIL PROTECTED] writes:
If we are going into code-lifting business, we should also consider
Pythons sre
What advantages does it have to make it worth considering?
Should be the same as pcre + support for wide chars.
--
Hannu
patterns
for the cache.
Perhaps the decision weather to try to use the cache at all could be
done at planning time depending on statistics information ?
Another idea is to make special regex type and store the regexes
pre-parsed (i.e. in some fast-load form) ?
--
Hannu Krosing [EMAIL PROTECTED
config files!! :P
Maybe support both, like for ANALYZE/ANALYSE ?
While at it, could we make another variant - ANALÜÜSI - which
would be native for me ;)
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
Tom Lane kirjutas K, 05.02.2003 kell 08:12:
Hannu Krosing [EMAIL PROTECTED] writes:
Another idea is to make special regex type and store the regexes
pre-parsed (i.e. in some fast-load form) ?
Seems unlikely that going out to disk could beat just recompiling the
regexp.
We have to get
storage format or as supported
client encoding ?
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
.
UTF-8 seems to be the most popular, but even XML standard requires all
compliant implementations to deal with at least both UTF-8 and UTF-16.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the
next int, you scan to the proper place and put it there (if it is not
there already).
Ordered lists are also much faster ( just O(N) ) to
compare/union/intersect.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe
Tom Lane kirjutas T, 11.02.2003 kell 18:39:
Bruno Wolff III [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] wrote:
Greg Stark [EMAIL PROTECTED] writes:
The neat thing is that hash aggregates would allow grouping on data types that
have = operators but no useful operator.
Hm.
function based on argument type
hannu=# create function f(int) returns int as 'select 1' language 'sql';
CREATE
hannu=# create function f(int,int) returns float as 'select 3.1415927'
language 'sql';
CREATE
hannu=# select f(1),f(1,1);
f | f
---+---
1 | 3.1415927
(1 row)
--
Hannu
Tom Lane kirjutas N, 13.02.2003 kell 20:10:
Curtis Faith [EMAIL PROTECTED] writes:
I don't dispute their conclusions in that context and under the
circumstances they outline of random distribution of deletion and
insertion values for the index keys. [But the random-distribution
Tom Lane kirjutas R, 14.02.2003 kell 01:13:
Hannu Krosing [EMAIL PROTECTED] writes:
But if we would allow the scans to find the same keys twice without ill
effects (as was suggested earlier, for using btrees to index arrays),
How is returning the same data twice not an ill effect?
From
Martin Matusiak kirjutas E, 17.02.2003 kell 16:53:
Greetings,
I am doing a project for college developing a java system utilizing a
RDBMS. The choice is between PostgreSQL and Oracle and I'm wondering
exactly how impossible would it be to make it compatible with both.
Postgre is said to be
Tom Lane kirjutas T, 18.02.2003 kell 17:21:
Kevin Brown [EMAIL PROTECTED] writes:
Tom Lane wrote:
The cases I've been able to study look like the header and a lot of the
following page data have been overwritten with garbage --- when it made
any sense at all, it looked like the contents
Tom Lane kirjutas K, 19.02.2003 kell 21:12:
Dave Cramer [EMAIL PROTECTED] writes:
Ok, if a patch were submitted to the parser to allow the syntax in
question would it be considered?
I would vote against it ... but that's only one vote.
Are you against it just on grounds of cleanliness and
Bruce Momjian kirjutas N, 20.02.2003 kell 06:16:
Agreed folks are going to have bigger problems from Informix than just
this, and in fact I used Informix for years and didn't know they allowed
this.
However, what solution do we have for UPDATE (coll...) = (select val...)
for folks? It is
Bruce Momjian kirjutas N, 20.02.2003 kell 06:16:
Agreed folks are going to have bigger problems from Informix than just
this, and in fact I used Informix for years and didn't know they allowed
this.
However, what solution do we have for UPDATE (coll...) = (select val...)
for folks? It is
Peter Eisentraut kirjutas T, 18.02.2003 kell 21:02:
Christopher Kings-Lynne writes:
REPLACE INTO anyone? ;)
The upcoming SQL 200x standard includes a MERGE command that appears to
fulfill that purpose.
Where is this upcoming standard available on net ?
Hannu
Tom Lane kirjutas E, 24.02.2003 kell 19:30:
Peter Eisentraut [EMAIL PROTECTED] writes:
Hey, I don't want to take your ILIKE away. But at the time it was added
the claim was that it was for compatibility and now we learn that that was
wrong.
This _is_ a compatibility feature, just not as
Michael Meskes kirjutas K, 26.02.2003 kell 13:00:
Did anyone ever think about creating a library that is able to handle
our numeric datatype? I'm currently thinking about adding this datatype
among others to the ones know to ecpg so no one is forced to convert
them or work on the strings. On
Chris Sutton kirjutas T, 04.03.2003 kell 17:03:
Hello,
I need some insight on the best way to use a RAM drive in a Postgresql
installation. Here is our situation and current setup:
Postgresql 7.2.1
Dual PIII 800
RAID 5 SCSI disks
Platypus 8GB PCI QikDrive (the RAM drive).
Hannu Krosing kirjutas T, 04.03.2003 kell 22:57:
Chris Sutton kirjutas T, 04.03.2003 kell 17:03:
Hello,
I need some insight on the best way to use a RAM drive in a Postgresql
installation. Here is our situation and current setup:
Postgresql 7.2.1
Dual PIII 800
RAID 5 SCSI
mlw kirjutas K, 05.03.2003 kell 22:05:
The idea of a RAM disk based database and reliable storage are in
complete opposition. Forget it.
I read from his post that the Platypus RAM disk _is_ his reliable
storage, just with some peculiar characteristics, like big transfer
speeds and uniform
Joe Conway kirjutas E, 10.03.2003 kell 05:35:
CREATE OR REPLACE FUNCTION array_push (anyarray, anyscalar)
RETURNS anyarray
AS '$libdir/plr','array_push'
LANGUAGE 'C';
could you make it
RETURNS typeof($1)
?
--
Hannu
---(end of
Tom Lane kirjutas P, 09.03.2003 kell 22:35:
However, this is going to create backwards-compatibility issues.
We have a few options for what to do:
1. Enforce the SQL spec requirement: error out if backwards fetch is
done when SCROLL wasn't given. But this will surely break a lot
of
Greg Stark kirjutas K, 12.03.2003 kell 07:10:
Marc G. Fournier [EMAIL PROTECTED] writes:
Personally ... as long as a v8.x client can talk to a v7.x backend, you
have my vote ... I'm more apt to upgrade my clients before my servers
anyway ...
Surely that's not true for a production
Tom Lane kirjutas K, 12.03.2003 kell 18:19:
Barry Lind [EMAIL PROTECTED] writes:
One addition I would personally like to see (it comes up in my apps
code) is the ability to detect wheather the server is big endian or
little endian. When using binary cursors this is necessary in order to
Tom Lane kirjutas N, 13.03.2003 kell 19:12:
Peter Eisentraut [EMAIL PROTECTED] writes:
OK, let's look at these more closely:
array_push(anyarray, anyelement) returns anyarray
The standard spelling for that appears to be
somearray || ARRAY[element]
which also has the nice
Hiroshi Inoue kirjutas N, 13.03.2003 kell 12:03:
Dave Page wrote:
Does looking up by the catalog keys take no cost ?
Obviously there is cost, but doing a lookup only on demand, has got to be
cheaper in the long run than including the entire column definition in the
message whether
Tom Lane kirjutas R, 14.03.2003 kell 19:15:
Greg Stark [EMAIL PROTECTED] writes:
So, just to throw out a wild idea: If you're talking about making large
changes to the on-the-wire protocol. Have you considered using an existing
database protocol?
Yeah, I have. Didn't look promising ---
Bruce Momjian kirjutas E, 17.03.2003 kell 20:49:
With no one replying on how to do correlated subqueries in FROM for
UPDATE,
Correlated subqueries not working in FROM cluse of UPDATE is IMHO a bug,
so the way to do correlated subqueries in FROM for UPDATE would be to
fix this bug ;)
All common
Tom Lane kirjutas K, 19.03.2003 kell 16:46:
Bruce Momjian [EMAIL PROTECTED] writes:
I wasn't sure it made logical sense to allow correlated subqueries in
FROM because the FROM is processed before the WHERE.
It doesn't; in fact it violates the whole semantic model of SQL,
as far as I can
On Wed, 2002-04-10 at 21:55, Justin Clift wrote:
Hannu Krosing wrote:
On Wed, 2002-04-10 at 16:32, Justin Clift wrote:
Hi everyone,
This is Prof. Bayer's response to the question is it alright to use
UB-Tree's in Open Source projects?.
Have you found out _what_ exaclty
On Thu, 2002-04-11 at 18:14, Tom Lane wrote:
Neil Conway [EMAIL PROTECTED] writes:
On the other hand, there are already a few reasons to make some
changes to the FE/BE protocol (NOTIFY messages, transaction state,
and now possibly PREPARE/EXECUTE -- anything else?).
Passing EXECUTE
On Thu, 2002-04-11 at 22:48, Tom Lane wrote:
Barry Lind [EMAIL PROTECTED] writes:
...
Since we
don't currently provide any information to the user on the relative cost
of the parse, plan and execute phases, the end user is going to be
guessing IMHO.
You can in fact get that
On Fri, 2002-04-12 at 03:04, Brian Bruns wrote:
On 11 Apr 2002, Hannu Krosing wrote:
IIRC someone started work on modularising the network-related parts with
a goal of supporting DRDA (DB2 protocol) and others in future.
That was me, although I've been bogged down lately, and haven't
On Sat, 2002-04-13 at 17:29, Tom Lane wrote:
[ way past time to change the title of this thread ]
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
OK, sounds fair. However, is there a more aggressive way of reclaiming the
space? The problem with updating all the rows to null for that
On Sun, 2002-04-14 at 08:48, Lamar Owen wrote:
Incidentally, the 7.2.93 (skipjack) public beta is a serious improvement over
RHL 7.2, and I personally recommend it, as KDE 3 is worth the upgrade, even
to a beta.
Is the 7.2.93 (skipjack) public beta an improvement in raw postgresql
On Tue, 2002-04-16 at 07:01, Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
How about this: We store the first 16 parameters in some fixed array for
fast access like now, and when you have more than 16 then 17 and beyond
get stored in some variable array in pg_proc.
itch
On Tue, 2002-04-16 at 03:20, Tatsuo Ishii wrote:
In my understanding, our consensus was enabling multibyte support by
default for 7.3. Any objection?
Is there currently some agreed plan for introducing standard
NCHAR/NVARCHAR types.
What does ISO/ANSI say about multybyteness of simple CHAR
On Wed, 2002-04-17 at 22:43, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
OTOH, it is also important where the file is on disk. As seen from disk
speed test graphs on http://www.tomshardware.com , the speed difference
of sequential reads is 1.5 to 2.5 between inner and outer
On Fri, 2002-04-19 at 05:28, Peter Eisentraut wrote:
Tom Lane writes:
Tatsuo Ishii [EMAIL PROTECTED] writes:
Can we enable syslog support by default for 7.3?
AFAIR, we agreed to flip the default some time ago, we just didn't
want to do it late in the 7.2 cycle. Go for it.
I
On Fri, 2002-04-19 at 08:15, Tatsuo Ishii wrote:
Can we enable syslog support by default for 7.3?
AFAIR, we agreed to flip the default some time ago, we just didn't
want to do it late in the 7.2 cycle. Go for it.
I think if no one complains about the lack of syslog on his
On Tue, 2002-04-23 at 01:29, Martijn van Oosterhout wrote:
The dumping is more of an extra, the original idea was to check for errors
in the datafiles. Hence the working name of pgfsck. At the moment the
dumping dumps only tuples where xmax == 0 but I'm not sure if that's
correct.
AFAIK it
On Tue, 2002-04-23 at 12:52, Martijn van Oosterhout wrote:
Well, from my thinking about how you would use these fields in a logical
way, it seems it's possible for xmax to be non-zero if the transaction
numbered xmax was not committed. But in that case (unless it was a delete)
there would be
On Thu, 2002-04-25 at 00:46, mlw wrote:
We have had several threads about index usage, specifically when PostgreSQL has
the choice of using one or not.
There seems to be a few points of view:
(1) The planner and statistics need to improve, so that erroneously using an
index (or not)
On Thu, 2002-04-25 at 08:42, Luis Alberto Amigo Navarro wrote:
(2) Use programmatic hints which allow coders specify which indexes are
used
during a query. (ala Oracle)
As I said before it would be useful a way to improve(not force) using
indexes on particular queries, i.e. lowering
On Thu, 2002-04-25 at 12:47, Curt Sampson wrote:
On Thu, 25 Apr 2002, Lincoln Yeoh wrote:
I think the raw partitions will be more trouble than they are worth.
Reading larger chunks at appropriate circumstances seems to be the low
hanging fruit.
That's certainly a good start. I don't
On Fri, 2002-04-26 at 07:38, Curt Sampson wrote:
On Thu, 25 Apr 2002, Bruce Momjian wrote:
WAL files are kept only until an fsync(), checkpoint, then reused.
One could keep them longer though, if one really wanted to.
Also, the info is tied to direct locations in the file. You could
On Fri, 2002-04-26 at 19:41, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
DB2 can run in two modes
1) similar to ours, where logs are reused after checkpoints/commits
allow it.
2) with log archiving: logs are never reused, but when system determines
it no longer needs them
On Mon, 2002-04-29 at 17:30, Tom Lane wrote:
Scott Marlowe [EMAIL PROTECTED] writes:
I've been thinking this over and over, and it seems to me, that the way
SETS in transactions SHOULD work is that they are all rolled back, period,
whether the transaction successfully completes OR NOT.
On Mon, 2002-04-29 at 17:53, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Perhaps we could do
SET SET TO LOCAL TO TRANSACTION;
Which would affect itself and all subsequent SET commands up to
SET SET TO GLOBAL;
or end of transaction.
This makes my head hurt. If I do
On Mon, 2002-04-29 at 18:20, Tom Lane wrote:
Thomas Lockhart [EMAIL PROTECTED] writes:
Rather than dismissing this out of hand, try to look at what it *does*
enable. It allows developers to tune specific queries without having to
restore values afterwards. Values or settings which may
On Tue, 2002-04-30 at 03:35, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Appears psql needs to know how to differentiate between it's own temp
tables and those of another connection.
More generally, psql is as yet clueless about schemas.
regression=# create schema foo;
CREATE
On Tue, 2002-04-30 at 03:35, Bruce Momjian wrote:
I think you have to use the backend pid to find your own. I think
there is a libpq function that returns the backend pis so psql can
frame the proper query.
Is anyoune working on information schema (or pg_xxx views) for use in
psql and
On Thu, 2002-05-02 at 05:33, Tom Lane wrote:
Nigel J. Andrews [EMAIL PROTECTED] writes:
So, how does one determine the current schema for temporary tables,
i.e. what name would be in search_path if it wasn't implicitly included?
The temp schema is pg_temp_nnn where nnn is your BackendId
On Thu, 2002-05-02 at 15:48, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
On Thu, 2002-05-02 at 05:33, Tom Lane wrote:
The temp schema is pg_temp_nnn where nnn is your BackendId (PROC array
slot number). AFAIK there isn't any exported way to determine your
BackendId from
On Thu, 2002-05-02 at 16:52, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Is PROC array slot number something internal to postgres ?
Yes.
If we used PID then we'd eventually have 64K (or whatever the range of
PIDs is on your platform) different pg_temp_nnn entries cluttering
101 - 200 of 1744 matches
Mail list logo
