Tom Lane wrote:
My patch counts inittapes(), tuplesort_begin_heap() and
tuplesort_begin_index(), and collect them, and sum them through the
stat collector.
Hm, that doesn't seem like quite the right level to be counting at.
Shouldn't you be hacking fd.c to count operations on
2. Think of a better defense against partial-page writes.
I like #2, or would if I could think of a better defense.
Ideas anyone?
FWIW, MSSQL deals with this using Torn Page Detection. This is off by
default (no check at all!), but can be abled on a per-database level.
Note that it only
On Thu, 30 Jun 2005, falcon wrote:
Hello, pgsql-hackers.
Hello, Oleg Bartunov.
Here are my first messages. Bug was found on these real data in a real table.
My hairs raised. Excuse my emotionality.
http://archives.postgresql.org/pgsql-bugs/2005-04/msg00160.php
--On Dienstag, Juni 28, 2005 01:43:27 +0200 Bernd Helmle
[EMAIL PROTECTED] wrote:
When altering a sequence created by a SERIAL column type (i do this by
examining pg_depend to avoid moving any other sequences that are
'foreign'), i need to recreate the default expression for the SERIAL
column
[sorry, resent because stalled]
Dear Stephen,
Right, it's a beginning to proper 'Role' support as defined by the SQL
specification.
Ok. AFAIC remember, the specification is pretty subtle and fuzzy enough so that
there is room for little design options.
I understand your concerns here
Satoshi Nagayasu [EMAIL PROTECTED] writes:
Tom Lane wrote:
Hm, that doesn't seem like quite the right level to be counting at.
Shouldn't you be hacking fd.c to count operations on FD_XACT_TEMPORARY
files?
Why do you think so?
I don't see tuplesort.c is good or not.
But all code of sort
On Thu, Jun 30, 2005 at 13:39:09 +0200,
Fabien COELHO [EMAIL PROTECTED] wrote:
The standard talks about 2 distinct concepts: USER and ROLE (4.34). I'm
not sure it is a good idea to drop the user concept to replace it by role.
If you do so, you may miss something about what roles are about.
Fabien,
* Fabien COELHO ([EMAIL PROTECTED]) wrote:
This is a very useful feature, and a key idea of the specs IMVVHO. ISTM
that the way fuse user and role misses that important point, as I have
not seen a set role in the grammar file.
'set role' is coming, sorry it wasn't in my initial
On AIX 5.3 with cvs head when trying to connect to the backend with
createuser or psql i get
psql: FATAL: unsupported frontend protocol 0.0: server supports 1.0 to 3.0
Help
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will
Dear Stephen,
Right, it's a beginning to proper 'Role' support as defined by the SQL
specification.
Ok. AFAIC remember, the specification is pretty subtle and fuzzy enough so
that there is room for little design options.
I understand your concerns here and while I agree with the basic
The TODO item is about counting all temporary files, not sorts in
particular. Or at least that's what I thought it meant.
If the DBA have to improve the performance,
DBA will need to know about:
- Which SQL generate a disk sort?
- Size of sorts.
- Changing 'work_mem' value can reduce
On Thu, 2005-06-30 at 23:02 +0900, Satoshi Nagayasu wrote:
The TODO item is about counting all temporary files, not sorts in
particular. Or at least that's what I thought it meant.
If the DBA have to improve the performance,
DBA will need to know about:
- Which SQL generate a disk
Dear Stephen,
Thanks again on working on this feature.
Role right resolution starts from the user and then works backwards up
the tree, with multi-level resolution. It wouldn't go past the logged
in user since that's really where it starts.
ISTM that the starting point should *not* be the
Dear Bruno,
The standard talks about 2 distinct concepts: USER and ROLE (4.34). I'm
not sure it is a good idea to drop the user concept to replace it by role.
If you do so, you may miss something about what roles are about.
I think it is a good idea to make users synonymous with roles with
Fabien Tom (if you're watching),
* Fabien COELHO ([EMAIL PROTECTED]) wrote:
Role right resolution starts from the user and then works backwards up
the tree, with multi-level resolution. It wouldn't go past the logged
in user since that's really where it starts.
ISTM that the starting
* Rod Taylor ([EMAIL PROTECTED]) wrote:
On Thu, 2005-06-30 at 23:02 +0900, Satoshi Nagayasu wrote:
The TODO item is about counting all temporary files, not sorts in
particular. Or at least that's what I thought it meant.
If the DBA have to improve the performance,
DBA will need to
Ciprian Popovici discovered an entirely new way to break the safety
interlocks that are meant to prevent you from starting a postmaster
in a data directory of the wrong version:
http://archives.postgresql.org/pgsql-general/2005-06/msg01349.php
While one could say this is pilot error, it's still
On Thu, Jun 30, 2005 at 09:16:01AM -0400, Samuel A Horwitz wrote:
On AIX 5.3 with cvs head when trying to connect to the backend with
createuser or psql i get
psql: FATAL: unsupported frontend protocol 0.0: server supports 1.0 to 3.0
This has been reported before -- I think the conclusion
Dave Page dpage@vale-housing.co.uk writes:
I've not been following the thread closely, so maybe this was already
proposed and rejected, but what about:
[4 functions]
That moves the goal posts somewhat.
Fair enough. The two you described are OK by me.
regards, tom
Stephen Frost [EMAIL PROTECTED] writes:
Tom, if you're watching, are you working on this? I can probably spend
some time today on it, if that'd be helpful.
I am not; I was hoping you'd deal with SET ROLE. Is it really much
different from SET SESSION AUTHORIZATION?
I'm pretty sure others
Hello, pgsql-hackers.
Sorry for fludding. Bug 1614 was fixed in 8.0.3. I just tests.
--
falcon mailto:[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
* Tom Lane ([EMAIL PROTECTED]) wrote:
Stephen Frost [EMAIL PROTECTED] writes:
Tom, if you're watching, are you working on this? I can probably spend
some time today on it, if that'd be helpful.
I am not; I was hoping you'd deal with SET ROLE. Is it really much
different from SET SESSION
On Thu, Jun 30, 2005 at 10:55:58AM -0400, Tom Lane wrote:
Ciprian Popovici discovered an entirely new way to break the safety
interlocks that are meant to prevent you from starting a postmaster
in a data directory of the wrong version:
Stephen Frost [EMAIL PROTECTED] writes:
I think one big issue is that we don't have a 'usage' database check
beyond pg_hba and so any user could get the schema definitions for any
database, which kind of sucks.
Not unless he can connect to it.
regards, tom lane
David Fetter [EMAIL PROTECTED] writes:
On Thu, Jun 30, 2005 at 10:55:58AM -0400, Tom Lane wrote:
Ciprian Popovici discovered an entirely new way to break the safety
interlocks that are meant to prevent you from starting a postmaster
in a data directory of the wrong version:
* Tom Lane ([EMAIL PROTECTED]) wrote:
Stephen Frost [EMAIL PROTECTED] writes:
I think one big issue is that we don't have a 'usage' database check
beyond pg_hba and so any user could get the schema definitions for any
database, which kind of sucks.
Not unless he can connect to it.
* Tom Lane ([EMAIL PROTECTED]) wrote:
Stephen Frost [EMAIL PROTECTED] writes:
That's controlled by pg_hba.conf though, isn't it? The idea being that
you'd like to give some people the ability to create users/roles, but to
limit the databases those created users/roles could connect to by,
Stephen Frost [EMAIL PROTECTED] writes:
That's controlled by pg_hba.conf though, isn't it? The idea being that
you'd like to give some people the ability to create users/roles, but to
limit the databases those created users/roles could connect to by, say,
requiring they have 'usage' or
On Jun 30, 2005, at 8:13 PM, Bernd Helmle wrote:
I currently recognized that a SERIAL column doesn't only create an
implicit sequence, it creates an implicit composite type with the
same name, too. I think this is the same for CREATE SEQUENCE?
Sequences are just special types of tables.
First, are WAL files not allowed to end in FF?
I was looking at the logs and it jumps straight from
0001019400FE to 00010195.
Yet other times it seems to end in an F: 0001019400EF.
Second, we have log archival enabled and the system it was archiving to
Tom,
Database pages. The current theory is that we can completely
reconstruct from WAL data every page that's been modified since the
last checkpoint. So the first write of any page after a checkpoint
dumps a full image of the page into WAL; subsequent writes only write
differences.
What
On Thu, Jun 30, 2005 at 11:42:59AM -0400, Tom Lane wrote:
David Fetter [EMAIL PROTECTED] writes:
On Thu, Jun 30, 2005 at 10:55:58AM -0400, Tom Lane wrote:
Ciprian Popovici discovered an entirely new way to break the safety
interlocks that are meant to prevent you from starting a postmaster
I wrote:
The least thing it should do is error out if *no* TCP/IP port could
be created while listen_addresses is set.
It's doing that now, and that should guard against the most common
problem, namemly the port already being occupied (since all TCP/IP
listen sockets use the same port).
Tom Lane wrote:
What I am speculating about is:
1. At postmaster start (or standalone backend start),
chdir into $PGDATA.
2. Henceforth, address everything under $PGDATA by
relative paths; don't use DataDir in the path at all.
This way, if someone moves
David Fetter wrote:
On Thu, Jun 30, 2005 at 11:42:59AM -0400, Tom Lane wrote:
Renaming data directories around is not that uncommon,
With all due respect, I believe that this falls under the category of
prying off cover plates. When people do this, they're responsible for
knowing
On Thu, Jun 30, 2005 at 02:31:01PM -0400, Andrew Dunstan wrote:
David Fetter wrote:
On Thu, Jun 30, 2005 at 11:42:59AM -0400, Tom Lane wrote:
Renaming data directories around is not that uncommon,
With all due respect, I believe that this falls under the category
of prying
Hi all,
Actually, I want to do some functions about
encrytation, but only i know the md5() function in postgresql. Do you know some
functions for 3des or des?
Thanks.
Jhon Carrillojdigital (a) cantv.net Caracas
- Venezuela
Getting my UnixWare box to be part of the buildfarm. Could one of the
knowledgeable hackers look at the failure for 'firefly' on REL7_4_STABLE and
tell me if it's ok?
Thanks.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail:
Josh Berkus josh@agliodbs.com writes:
What I'm confused about is that this shouldn't be anything new for 8.1. Yet
8.1 has *worse* performance on the STP machines than 8.0 does, and it's
pretty much entirely due to this check.
That's simply not believable --- better recheck your analysis.
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 29 June 2005 12:46
To: Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
I have a new idea --- pg_storage_size().
I'm not against that one, but I
On Jun 30, 2005, at 5:48 PM, Dave Page wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 29 June 2005 12:46
snip /
I have a new idea --- pg_storage_size().
I'm not against that one, but I think Tom's point is vaild. I cannot
think of anything better at
-Original Message-
From: Michael Glaesemann [mailto:[EMAIL PROTECTED]
Sent: 30 June 2005 10:01
To: Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
I'm still unclear as to what exactly is trying to be captured by the
I have a new idea --- pg_storage_size().
I'm not against that one, but I think Tom's point is vaild. I cannot
think of anything better at the moment though (maybe pg_component_size,
but that's equally random) :-(
Anyone else? Please? Someone? Anyone? :-)
Maybe pg_trait_size() or
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 30 June 2005 10:29
To: Bruce Momjian; Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
Maybe pg_trait_size() or pg_property_size() will do?
I
Dave Page dpage@vale-housing.co.uk writes:
Thanks Michael. We have 2 functions - 1 returns the on disk size of a
table or index without any additional parts such as indexes or toast
tables. The other function returns the total on disk size of a table and
all associated indexes and toast tables
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 30 June 2005 14:41
To: Dave Page
Cc: Michael Glaesemann; PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
Dave Page dpage@vale-housing.co.uk writes:
Thanks Michael.
Tom Lane [EMAIL PROTECTED] writes:
This way, if someone moves a data directory with a running postmaster
in it, nothing breaks at all. It would probably run a bit faster too,
since file open calls would have fewer directories to traverse through.
On reasonable platforms the time spent
Andrew Dunstan [EMAIL PROTECTED] writes:
Maybe I have misunderstood. Could the backends not chdir into the db
subdir and then do everything relative to that (using .. if necessary)?
If we do that then the path to things from the postmaster is different
than it is for the children, which is
Greg Stark [EMAIL PROTECTED] writes:
However it might be nice to have dumps go to a configurable place.
You'd have to talk to your kernel provider about that one; we don't have
any direct control over where or even whether core dumps occur.
There's another approach that seems more robust.
Tom,
What I'm confused about is that this shouldn't be anything new for
8.1. Yet 8.1 has *worse* performance on the STP machines than 8.0
does, and it's pretty much entirely due to this check.
That's simply not believable --- better recheck your analysis. If 8.1
is worse it's not
Rod Taylor [EMAIL PROTECTED] writes:
First, are WAL files not allowed to end in FF?
I recall that there's some wastage of addressing space, but I don't
recall the exact reasoning. You can probably find a comment about it
in xlog.c or nearby.
However, now I'm left with a pg_xlog directory that
On 6/30/05, Dave Page dpage@vale-housing.co.uk wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 29 June 2005 12:46
To: Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
I have a new idea
However, now I'm left with a pg_xlog directory that is about 7 GB in
size. All of the files but the most recent has a corresponding
archive_status/$FILE.done file. Will PostgreSQL eventually remove most
of these unnecessary files or am I stuck with them?
I'd have thought the next
Peter Eisentraut [EMAIL PROTECTED] writes:
Reading the comments in StreamServerPort, it seems the only problem we
can't go fatal error everywhere is that on some systems the IPv4 and
IPv6 sockets fight each other when bind() is called. For the other
failure modes, it seems that no such
Dawid Kuroczko wrote:
On 6/30/05, Dave Page dpage@vale-housing.co.uk wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 29 June 2005 12:46
To: Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
I have a
Larry Rosenman ler@lerctr.org writes:
Getting my UnixWare box to be part of the buildfarm. Could one of the
knowledgeable hackers look at the failure for 'firefly' on REL7_4_STABLE and
tell me if it's ok?
Looks OK to me. The more recent branches use a stronger ORDER BY to
prevent that
Tom Lane [EMAIL PROTECTED] writes:
Greg Stark [EMAIL PROTECTED] writes:
However it might be nice to have dumps go to a configurable place.
You'd have to talk to your kernel provider about that one; we don't have
any direct control over where or even whether core dumps occur.
Well on most
Greg Stark [EMAIL PROTECTED] writes:
For that matter, would depending on the cwd interact well with trusted Pl
languages that can change the cwd?
That would definitely be in the category of don't do that --- but
there are such a long list of ways to hose your backend in a trusted PL
that adding
Do the transaction id's used in 2PC need to be unique across all
sessions?
Do we provide a mechanism for this ?
If not shouldn't we provide a way to create a unique transaction id ?
Dave Cramer
[EMAIL PROTECTED]
www.postgresintl.com
ICQ #14675561
jabber [EMAIL PROTECTED]
ph (519 939 0336 )
Dave Page wrote:
That would do just the
toast/index/heap, and pg_relation_size() gets a total of them all, and
only works on heap, no index or toast.
The totalling version (whatever it ends up being called) should
definitely work on toast tables, as it is a legitimate use case to want
[EMAIL PROTECTED] wrote:
I have a new idea --- pg_storage_size().
I'm not against that one, but I think Tom's point is vaild. I cannot
think of anything better at the moment though (maybe pg_component_size,
but that's equally random) :-(
Anyone else? Please? Someone? Anyone? :-)
In reality all it takes is a sequence, however if it were system
generated it would be simpler
Dave
On 30-Jun-05, at 6:46 PM, Alvaro Herrera wrote:
On Thu, Jun 30, 2005 at 06:39:43PM -0400, Dave Cramer wrote:
Do the transaction id's used in 2PC need to be unique across all
sessions?
Dave Cramer wrote:
Do the transaction id's used in 2PC need to be unique across all sessions?
They are global IDs, yes.
Do we provide a mechanism for this ?
If not shouldn't we provide a way to create a unique transaction id ?
Well, in XA the XIDs are assigned by the TM, the individual
I'm thinking of the situation where one transaction occurs on more
than one backend, and there is
more than one transaction manager.
Dave
On 30-Jun-05, at 7:37 PM, Oliver Jowett wrote:
Dave Cramer wrote:
Do the transaction id's used in 2PC need to be unique across all
sessions?
They
Bruce Momjian pgman@candle.pha.pa.us writes:
I don't think so. I think trait and property suggests an aspect of the
object, so saying trait/property size is saying I am talking about an
aspect of the object, while for a heap, its size is really its size, it
isn't an aspect of its size.
I
Dave Cramer wrote:
I'm thinking of the situation where one transaction occurs on more than
one backend, and there is
more than one transaction manager.
XA XIDs are *global* IDs, i.e. they are unique even with more than one
TM involved. It's the responsibility of the TM to generate a
Oliver Jowett wrote:
If you have two different databases involved in the same global
transaction, then yes, the two backends could be told to use the same
global XID. That's normal. (they don't *have* to be given the same XID
as they could be participating in two independent branches of the
On 30-Jun-05, at 8:00 PM, Oliver Jowett wrote:
Dave Cramer wrote:
I'm thinking of the situation where one transaction occurs on
more than
one backend, and there is
more than one transaction manager.
XA XIDs are *global* IDs, i.e. they are unique even with more than one
TM involved.
Dave Cramer [EMAIL PROTECTED] writes:
Do the transaction id's used in 2PC need to be unique across all
sessions?
Do we provide a mechanism for this ?
If not shouldn't we provide a way to create a unique transaction id ?
I see no value in that at all. The point of 2PC is to synchronize with
Oliver Jowett [EMAIL PROTECTED] writes:
Can we make the GID-to-internal-xid mapping for prepared transactions
1:N rather than the current 1:1?
No.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our
Tom Lane wrote:
Oliver Jowett [EMAIL PROTECTED] writes:
Can we make the GID-to-internal-xid mapping for prepared transactions
1:N rather than the current 1:1?
No.
Ok, so how do we get XA working when a single global transaction
involves two databases on the same cluster?
The scenario is:
Oliver Jowett [EMAIL PROTECTED] writes:
Ok, so how do we get XA working when a single global transaction
involves two databases on the same cluster?
It's the TM's responsibility to deal with that. I would expect it to
hand out transaction IDs that consist of a common prefix and a
per-database
Euler Taveira de Oliveira [EMAIL PROTECTED] writes:
I think that moving rtree_gist, reindexdb, and/or userlock into core
would have to happen before feature freeze,
[snip]
Are you think in putting reindex at core? I was about to submit a
replacement of it but if it goes to bin/scripts (for
Hi Tom,
I think that moving rtree_gist, reindexdb, and/or userlock into core
would have to happen before feature freeze,
[snip]
Are you think in putting reindex at core? I was about to submit a
replacement of it but if it goes to bin/scripts (for example) I can
rearrange the patch. Could I?
Bruce - this is done:
o Add dumping and restoring of LOB comments
Chris
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Tom Lane wrote:
Oliver Jowett [EMAIL PROTECTED] writes:
Ok, so how do we get XA working when a single global transaction
involves two databases on the same cluster?
It's the TM's responsibility to deal with that. I would expect it to
hand out transaction IDs that consist of a common
Oliver Jowett wrote:
Tom Lane wrote:
It's the TM's responsibility to deal with that. I would expect it to
hand out transaction IDs that consist of a common prefix and a
per-database suffix, if it does not know which resources it's dealing
with might share a common GID namespace.
I don't know
Why was that approved to -announce? What does it have to do with
PostgreSQL announcements?
Marc G. Fournier wrote:
For those that remember far enough back, you will have *cough* fond
memories of Al Dev ... he seems to have resurfaced, and I figured that
this enlightened posting might be a
For those that remember far enough back, you will have *cough* fond
memories of Al Dev ... he seems to have resurfaced, and I figured that
this enlightened posting might be a nice end to a week for some :)
On Thu, 30 Jun 2005, Al_Dev wrote:
Since PostgreSQL, MySQL is written in C, there
On Thu, Jun 30, 2005 at 10:17:52AM -0400, Ing. Jhon Carrillo - Caracas,
Venezuela wrote:
Actually, I want to do some functions about encrytation, but only
i know the md5() function in postgresql. Do you know some functions
for 3des or des?
Have you looked at contrib/pgcrypto?
BTW, this
80 matches
Mail list logo
