Hello all,
I'm trying to modify the storage manager now.
I found a number of smgrs are stored separately in the storage manager
module (NSmgr in smgr.c and NStorageManagers in smgrtype.c),
and names of storage managers are stored in smgrtype.c.
Are there any reason for this?
I think they shold
On Tue, 2004-10-19 at 02:45, Andrew Dunstan wrote:
*shrug* OK. Then plperl should probably not be regarded as being as
trusted as we would like. Note that old versions of Safe.pm have been
the subject of security advisories such as this one
http://www.securityfocus.com/bid/6111/info/ for
Satoshi Nagayasu [EMAIL PROTECTED] writes:
I'm trying to modify the storage manager now.
Um ... why?
There is no doubt that the current smgr interface leaves a lot to be
desired, but the reason that it's in such sad shape is that there is
absolutely no modern-day use for an API at that
I'm trying to modify the storage manager now.
Um ... why?
Because I want to add my new storage manager.
It is not just for (single) magnetic disk.
If anyone had wanted to add a new storage manager in the last fifteen
years, we'd doubtless have tried to clean this up some, but no one has
To stop everyone asking me - I will still be working on phpPgAdmin, no
need to panic :)
Next release of phpPgAdmin should be at the same time as 8.0 PostgreSQL.
Chris
Christopher Kings-Lynne wrote:
Hi everyone,
I think I'll be taking some time off from the PostgreSQL project, to
work on other
Hallo!
I would like to know if there are any discussions
about managing directories from Postgresql Datnbank
System. Or knows anybody how to manage it?
Thanks
___
Gesendet von Yahoo! Mail -
Postgres 7.0.2
Problem
---
I am having a rather
big problem with an installation of postgres 7.0.2 on cobalt, in that the db
server is unable to see any of the data stored in the (only) database which is
running (other than template1). I suspect that the
Enjoy the break :) Hints as to the 'other stuff' that is more intersting
then PostgreSQL? :) Or is it secret ... ?
On Tue, 19 Oct 2004, Christopher Kings-Lynne wrote:
To stop everyone asking me - I will still be working on phpPgAdmin, no need
to panic :)
Next release of phpPgAdmin should be
Neil Conway wrote:
On Tue, 2004-10-19 at 02:45, Andrew Dunstan wrote:
*shrug* OK. Then plperl should probably not be regarded as being as
trusted as we would like. Note that old versions of Safe.pm have been
the subject of security advisories such as this one
On Tue, Oct 19, 2004 at 08:47:20AM -0400, Andrew Dunstan wrote:
But maybe we can just live with what we have and advertise that 8.0's
plperl is more secure.
The release notes should point out that 7.4's plperl is unsecure unless
the correct version of Safe.pm is installed. Maybe it works to
The command-line argument parsing in pg_ctl is not portable. This is the
output on a glibc system:
$ pg_ctl start stop
pg_ctl: too many command-line arguments (first is start)
But:
$ POSIXLY_CORRECT=1 pg_ctl start stop
pg_ctl: too many command-line arguments (first is stop)
This is probably
o fix shared memory on Win2k terminal server
We might be able to just mark this as not supported.
I have attached a patch that I think fixes this. The problem I saw
and fixed is, that the shmem created in a terminal services client is not
visible to the console (or
On 10/12/2004 4:02 PM Tom Lane could be overheard saying::
Marcos A Vaz Salles [EMAIL PROTECTED] writes:
In order to make index selection possible, we
have extended the PostgreSQL DBMS to allow the simulation of
hypothetical indexes. We believe these server extensions may be of
value for
Am Montag, 18. Oktober 2004 19:43 schrieb Tom Lane:
An alternative possibility is to stop pretending that pgport is agnostic
about whether it is in backend or frontend. This might mean some
duplication of code between src/port/ and src/backend/port/, but if
that's what it takes to have sane
On Tue, Oct 19, 2004 at 01:28:52PM +0100, Ben Osborne wrote:
Postgres 7.0.2 Problem
---
Yikes. That's old.
(only) database which is running (other than template1). I suspect that the
files in the data directory have been conrrupted or otherwise lost
Neil Conway [EMAIL PROTECTED] writes:
Granted, but I think you've mostly conceded my point: every _subsequent_
time TAS() is invoked, the non-locking test is a clear win (with the
possible exception of PPC).
I'm not real sure. One point here is that the standard advice about
this stuff is
Marc G. Fournier wrote:
Enjoy the break :) Hints as to the 'other stuff' that is more
intersting then PostgreSQL? :) Or is it secret ... ?
It's probably just a joke. Can you imagine something more interesting
than PostgreSQL?!?
Regards,
Andreas
---(end of
On Thu, Oct 14, 2004 at 09:49:47AM +0200, [EMAIL PROTECTED] wrote:
Dear Sirs,
I would like to know if there are any discussions about
creating an embedded version on postgresql. My thoughts
go towards building/porting a sqlite equivalent of pg.
The discussion comes up occasionally. After
Ben Osborne [EMAIL PROTECTED] writes:
Postgres 7.0.2 Problem
I am having a rather big problem with an installation of postgres 7.0.2 on
cobalt, in that the db server is unable to see any of the data stored in the
(only) database which is running (other than template1).
The symptoms seem
Philip Warner [EMAIL PROTECTED] writes:
To solve this, we should dump the table definition as a format string and
dump the tablespace clause (ie. ' TABLESPACE ts') as a separate part of the
table definition TOC entry. If the user wants the tablespace to be dumped,
then we substitute the
At 03:06 AM 20/10/2004, Tom Lane wrote:
I think the tricky part of that would be inserting the tablespace clause
in the right place; for CREATE INDEX this seems to require nontrivial
parsing. (Both the index column definitions and the WHERE clause could
be arbitrarily complicated expressions.)
Philip Warner [EMAIL PROTECTED] writes:
At 03:06 AM 20/10/2004, Tom Lane wrote:
I think the tricky part of that would be inserting the tablespace clause
in the right place; for CREATE INDEX this seems to require nontrivial
parsing. (Both the index column definitions and the WHERE clause could
On 10/19/2004 12:11 PM, Andreas Pflug wrote:
Marc G. Fournier wrote:
Enjoy the break :) Hints as to the 'other stuff' that is more
intersting then PostgreSQL? :) Or is it secret ... ?
It's probably just a joke. Can you imagine something more interesting
than PostgreSQL?!?
There comes the time
On 10/19/2004 11:41 AM, Andrew Sullivan wrote:
On Tue, Oct 19, 2004 at 01:28:52PM +0100, Ben Osborne wrote:
Postgres 7.0.2 Problem
---
Yikes. That's old.
(only) database which is running (other than template1). I suspect that the
files in the data directory have
GB:
I would like to know if there are any discussions about
creating an embedded version on postgresql. My thoughts
go towards building/porting a sqlite equivalent of pg.
Not that I personally know of.While it would be nice to have an embeddable
database which was syntax-compatible with
There comes the time in every hackers life when he discovers that even
unsuccessfully chasing girls can be more fun than debugging kernel
modules or interface libraries. Some get over that phase without greater
collateral damage, some become successfull in the chasing, some then get
caught by
At 03:25 AM 20/10/2004, Tom Lane wrote:
Maybe there's something I don't understand. How are you expecting
pg_restore to control whether it outputs the command with a TABLESPACE
clause embedded or not, if pg_dump has already built the command string
that way?
This will only work if we modify the
Philip Warner [EMAIL PROTECTED] writes:
DEFINITION: CREATE TABLE fred ... %%tablespace%% ...
TABLESPACE: ' TABLESPACE t'
pg_restore would read these, and use the settings from the command line to
either substitute an empty string or the TABLESPACE text for %%tablespace%%
in the DEFINTION.
On Tue, 19 Oct 2004, Jan Wieck wrote:
On 10/19/2004 12:11 PM, Andreas Pflug wrote:
Marc G. Fournier wrote:
Enjoy the break :) Hints as to the 'other stuff' that is more intersting
then PostgreSQL? :) Or is it secret ... ?
It's probably just a joke. Can you imagine something more interesting
On Oct 19, 2004, at 2:05 PM, Joshua D. Drake wrote:
There comes the time in every hackers life when he discovers that
even unsuccessfully chasing girls can be more fun than debugging
kernel modules or interface libraries. Some get over that phase
without greater collateral damage, some become
http://secunia.com/advisories/12860/
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Hello!
I wrote this css file 2 years ago. It's very useful when using docs.
Can you add it in mainstream?
Thanks.
Nurlan MukhanovBODY { font-family : Tahoma; font-size : 8pt; color : #33; background: #FF; }
A:LINK { color : #66; }
A:HOVER { color : #CC;text-decoration :
Hello Josh,
I will take a look at pgFoundry and register a new project for index
selection. I will also look for other projects there that we may help
somehow. About the tutorial, I will send you the presentation we used
to generate the web pages so that you can see it with OpenOffice. ;)
Tom Lane wrote
In any case, whether or not you think DETERMINISTIC means IMMUTABLE,
Tom, Your knowledge of the confusing bits of the standard puts us all to
shame.
Troels did have a point, which was to do with standards conformance and
compatibility. The main point at issue is whether someone
Mark Kirkwood wrote
Tom Lane wrote:
I believe that the term bitmap index is also used with a different
meaning wherein it actually does describe a particular kind of on-disk
index structure, with one bit per table row.
IMHO building in-memory bitmaps (the first idea) is a very good idea
Tom Lane wrote:
Info: resolving _my_exec_path by linking to __imp__my_exec_path (auto-import)
fu01.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
nmth00.o(.idata$4+0x0): undefined reference to `_nm__my_exec_path'
I was wondering whether my_exec_path might need to be
On Tue, Oct 19, 2004 at 11:22:31PM +0100, Simon Riggs wrote:
I was thinking about this recently, then realised that building the bitmap
would not be as easily, since PostgreSQL doesn't index null values. That
would mean that the sets of CTIDs in each index would be disjoint. My
thinking about
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
I was wondering whether my_exec_path might need to be marked DLLIMPORT.
Not sure about the other symbol though.
Is this going to be fixed? Right now tsearch2 is totally busted for
Windows. I would fix it but my attempt (marking
Simon Riggs wrote:
I believe that the benefit of on-disk bitmap indexes is supposed to be
reduced storage size (compared to btree).
The main problem is the need for the table to be read-only. Until we have
partitioning, we wouldn't be able to easily guarantee parts of a table as
being
Simon Riggs [EMAIL PROTECTED] writes:
I was thinking about this recently, then realised that building the bitmap
would not be as easily, since PostgreSQL doesn't index null values.
As Alvaro already pointed out, this statement is bogus; and I'm not sure
what it has to do with the topic anyway.
Tom,
I've been taking bitmap to be a rather handwavy way of saying a
compact representation of sets of CTIDs that is readily amenable to
being ANDed and ORed with other sets.
Well, actually I think we're talking about two different features:
1) a way to use more than one index per
Nurlan M. Mukhanov wrote:
I wrote this css file 2 years ago. It's very useful when using docs.
Can you add it in mainstream?
http://jigsaw.w3.org/css-validator/ should be your first stop. After
that, you can write to [EMAIL PROTECTED] with an explanation
about what your stylesheet does and
On Tue, 19 Oct 2004, Josh Berkus wrote:
Tom,
I've been taking bitmap to be a rather handwavy way of saying a
compact representation of sets of CTIDs that is readily amenable to
being ANDed and ORed with other sets.
Well, actually I think we're talking about two different features:
1)
Tom Lane
Simon Riggs [EMAIL PROTECTED] writes:
How would you dynamically build the bit maps from the indexes?
Or would you:
- copy aside and sort the indexes on CTID
- merge join them all to find matching CTIDs
- probe into the main table
I've been taking bitmap to be a rather
Alvaro Herrera
On Tue, Oct 19, 2004 at 11:22:31PM +0100, Simon Riggs wrote:
I was thinking about this recently, then realised that building the
bitmap
would not be as easily, since PostgreSQL doesn't index null values. That
would mean that the sets of CTIDs in each index would be disjoint.
At 04:20 AM 20/10/2004, Tom Lane wrote:
Nope. I can break that trivially, eg:
Thats why in my first message I mentioned escaping and unescaping all '%'
in the deinition.
There's also the nontrivial matter of how pg_dump would decide where to
insert the %%tablespace%% string into the CREATE
Tom == Tom Lane [EMAIL PROTECTED] writes:
Tom One huge advantage is that the actual heap visiting becomes
Tom efficient, eg you never visit the same page more than once.
Tom (What you lose is the ability to retrieve data in index
Tom order, so this isn't a replacement for
Enjoy the break :) Hints as to the 'other stuff' that is more
intersting then PostgreSQL? :) Or is it secret ... ?
It's probably just a joke. Can you imagine something more interesting
than PostgreSQL?!?
www.planeshift.it
(Sorry for the sucky flash intro :/)
I've been wanting to get into some
On Tue, 19 Oct 2004, Sailesh Krishnamurthy wrote:
Tom == Tom Lane [EMAIL PROTECTED] writes:
Tom One huge advantage is that the actual heap visiting becomes
Tom efficient, eg you never visit the same page more than once.
Tom (What you lose is the ability to retrieve data in index
On Wed, 2004-10-20 at 06:18, Rod Taylor wrote:
http://secunia.com/advisories/12860/
This seems like a rather inconsequential problem, but it should be
fixed. The first two ideas that come to mind: use temporary files in
$PWD rather than /tmp, or create a subdirectory in /tmp to use for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Has a MySQL backend unfortunately - maybe I can convert them :)
We might not let you back otherwise! :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200410192349
-BEGIN PGP SIGNATURE-
On Wed, Oct 20, 2004 at 12:52:57PM +1000, Neil Conway wrote:
On Wed, 2004-10-20 at 06:18, Rod Taylor wrote:
http://secunia.com/advisories/12860/
This seems like a rather inconsequential problem, but it should be
fixed. The first two ideas that come to mind: use temporary files in
$PWD
Neil Conway [EMAIL PROTECTED] writes:
On Wed, 2004-10-20 at 06:18, Rod Taylor wrote:
http://secunia.com/advisories/12860/
This seems like a rather inconsequential problem,
Indeed, since ordinary users have no use for make_oidjoins_check.
It's surely very implausible that anyone would run it
Alvaro Herrera [EMAIL PROTECTED] writes:
Better, use mktemp(1). The thread testing script already does it IIRC.
There are only two uses of mktemp(1) in our source tree: configure and
config.guess. Both were gotten from elsewhere, and both jump through
some seriously unreadable hoops in order
On Wed, Oct 20, 2004 at 12:31:11AM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Better, use mktemp(1). The thread testing script already does it IIRC.
There are only two uses of mktemp(1) in our source tree: configure and
config.guess. Both were gotten from elsewhere,
55 matches
Mail list logo
