Hello, Josh.
You wrote:
JB All,
JB For 9.1, I'm trying to get beta testing a *bit* more organized in hopes
JB of shortening the beta period. Since we're not up and running on Django
JB on the main website yet, and thus I can't make an app for collecting
JB test reports, I've created a Google
On Wed, 2011-04-06 at 07:47 +0300, Peter Eisentraut wrote:
On tis, 2011-04-05 at 16:04 -0700, Joshua D. Drake wrote:
Well any libpq app but yes. I actually wonder as to the legitmacy of
having both a pgpass and a pg_service. Why not just one of them?
So you can keep passwords in a safer
On Tue, Apr 05, 2011 at 11:55:04PM -0700, Joshua D. Drake wrote:
I want to achieve two things:
1. More understandable .pgpass format. Yes, I understand our standard
format, most people won't. Like JoshB said, hard to debug.
This I understand.
2. psql foo, gets me into foo. A macro for
On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake j...@commandprompt.com wrote:
I want to achieve two things:
1. More understandable .pgpass format. Yes, I understand our standard
format, most people won't. Like JoshB said, hard to debug.
How about allowing '#'-comments there and putting field
Well at the minute I am trying to find out sections of postgresql that can be
helpful to carry out a database forensics analysis and thought the most
useful with be the transaction log. So was actually interested in viewing
it.
--
View this message in context:
How does this relate to the existing pqc project (
http://code.google.com/p/pqc/)? Seems the goals are fairly similar, and both
are based off pgpool?
/Magnus
On Apr 6, 2011 2:10 AM, Masanori Yamazaki m.yamazak...@gmail.com wrote:
Hello
My name is Masanori Yamazaki. I am sending my proposal
Came across the following in a paper from Oct 2010. Was wondering is this is
old news I missed in this group.
http://pdos.csail.mit.edu/papers/linux:osdi10.pdf
about Linux optimization on multi-core CPU's.
The group at MIT were exploring how some Linux apps were scaling up ---
sometimes badly,
Hello
I am sending my proposal about Google Summer Of Code2011.
It would be nice if you could give me your opinion.
・title
Caching query results in pgpool-II
・Synopsis
Pgpool-II has query caching functionality using storage provided by
dedicated PostgreSQL (system database). This has
On 05.04.2011 20:11, Jan-Erik Lärka wrote:
Yes, it's the successor to OS/2, eComStation.
We don't currently have anyone active in the community running on that
platform, so I'm reluctant to add those codepage aliases as I won't be
able to test it, and we don't support OS/2 anyway. But if
A quick review of the open items list suggests that we have three main
areas that need attention before we can declare ourselves ready for
beta.
In no particular order:
1. There are a bunch of small, outstanding SSI patches.
2. Bugs - plural - related to pg_upgrade typed tables.
3. Assorted
On Wed, Apr 6, 2011 at 6:49 AM, aaronenabs aaronen...@btconnect.com wrote:
Well at the minute I am trying to find out sections of postgresql that can be
helpful to carry out a database forensics analysis and thought the most
useful with be the transaction log. So was actually interested in
On Tue, Apr 5, 2011 at 2:21 PM, Mischa Sandberg
mischa.sandb...@sophos.com wrote:
Came across the following in a paper from Oct 2010. Was wondering is this is
old news I missed in this group.
http://pdos.csail.mit.edu/papers/linux:osdi10.pdf
about Linux optimization on multi-core CPU’s.
Robert Haas robertmh...@gmail.com writes:
... Most urgently, I believe we need a bit more committer bandwidth. I
believe that I could tackle either the SSI patches or the pg_upgrade
typed tables issue, or I could try to make a dent in the collation
stuff, but I don't think I can cover two of
Marko Kreen mark...@gmail.com writes:
On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake j...@commandprompt.com
wrote:
1. More understandable .pgpass format. Yes, I understand our standard
format, most people won't. Like JoshB said, hard to debug.
How about allowing '#'-comments there and
True, i have looked at pg_dumpfile and worked around that, Seems to be a very
important tool for forensic investigations. But looking for any other aspect
of the DBMS that can be helpful.
--
View this message in context:
On Mar 28, 2011, at 1:29 AM, Pavel Stehule wrote:
Is there some simple possibility to check a rights from stored procedure?
Well, there's the catalog lookup method:
SELECT EXISTS (SELECT 1 FROM pg_catalog.pg_roles WHERE rolname=$1 AND
rolsuper)
Is that what you had in mind?
I found
On Mar 30, 2011, at 3:45 PM, Jan Wieck wrote:
What I would envision for DDL triggers is that they first don't fire on an
object type, but rather on a command completion code, like CREATE TABLE or
DROP SCHEMA.
To do anything useful with that of course would require that all DDL does go
On Wed, Apr 6, 2011 at 9:42 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
... Most urgently, I believe we need a bit more committer bandwidth. I
believe that I could tackle either the SSI patches or the pg_upgrade
typed tables issue, or I could try to make
On Wed, Apr 6, 2011 at 9:48 AM, aaronenabs aaronen...@btconnect.com wrote:
True, i have looked at pg_dumpfile and worked around that, Seems to be a very
important tool for forensic investigations. But looking for any other aspect
of the DBMS that can be helpful.
pageinspect is useful.
Also
Robert Haas robertmh...@gmail.com writes:
I agree. But again, that's not really what I'm focusing on - the
collations stuff, the typed tables patch, and SSI all need serious
looking at, and I'm not sure who is going to pick all that up.
Well, I'll take responsibility for collations. If I get
Thanks for that information would look into the xmin and xmax columns.
so its not possible to turn the HeapTupleVisiblity to true to view dead
tuples by setting it to
#define HeapTupleSatisfiesVisibility(tuple, snapshot, buffer)(1)
--
View this message in context:
On Wed, Apr 6, 2011 at 11:13 AM, aaronenabs aaronen...@btconnect.com wrote:
Thanks for that information would look into the xmin and xmax columns.
so its not possible to turn the HeapTupleVisiblity to true to view dead
tuples by setting it to
#define HeapTupleSatisfiesVisibility(tuple,
On Tue, Apr 05, 2011 at 09:44:44AM -0400, Robert Haas wrote:
On Wed, Mar 30, 2011 at 9:32 PM, Noah Misch n...@leadboat.com wrote:
On Wed, Mar 30, 2011 at 07:50:12PM +0300, Peter Eisentraut wrote:
Here is a patch that addresses this problem.
This only works when exactly one typed table
On 06.04.2011 18:02, Tom Lane wrote:
Robert Haasrobertmh...@gmail.com writes:
I agree. But again, that's not really what I'm focusing on - the
collations stuff, the typed tables patch, and SSI all need serious
looking at, and I'm not sure who is going to pick all that up.
Well, I'll take
On Wed, Apr 6, 2011 at 12:06 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 06.04.2011 18:02, Tom Lane wrote:
I agree. But again, that's not really what I'm focusing on - the
collations stuff, the typed tables patch, and SSI all need serious
looking at, and I'm not sure
Robert Haas robertmh...@gmail.com wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
I can look at the SSI patches, but not until next week, I'm
afraid. Robert, would you like to pick that up before then? Kevin
Dan have done all the heavy lifting, but it's nevertheless
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Robert Haas robertmh...@gmail.com wrote:
... The one I'm most
worried about is SSI: three different HTABs contend for shared
memory in a free-for-all - because there's no patch for that yet,
and I am wary of breaking something mucking around
On 06.04.2011 17:46, Tom Lane wrote:
Kevin Grittnerkevin.gritt...@wicourts.gov writes:
Robert Haasrobertmh...@gmail.com wrote:
... The one I'm most
worried about is SSI: three different HTABs contend for shared
memory in a free-for-all - because there's no patch for that yet,
and I am wary
On 6 April 2011 17:57, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 06.04.2011 17:46, Tom Lane wrote:
Kevin Grittnerkevin.gritt...@wicourts.gov writes:
Robert Haasrobertmh...@gmail.com wrote:
... The one I'm most
worried about is SSI: three different HTABs contend for
Robert Haas robertmh...@gmail.com writes:
On Wed, Apr 6, 2011 at 11:13 AM, aaronenabs aaronen...@btconnect.com wrote:
Thanks for that information would look into the xmin and xmax columns.
so its not possible to turn the HeapTupleVisiblity to true to view dead
tuples by setting it to
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
On 06.04.2011 17:46, Tom Lane wrote:
I confess to not having been reading the discussions about SSI very
much, but ... do we actually care whether there's a free-for-all?
What's the downside to letting the remaining shmem get
Wow sounds very complicated. Will have to try that but got to say i am new to
postgresql and might find that difficult. so at the moment i would try and
to the little i can to find parts in the DBMS that can be of use, as i
already tried struggling to try and find a way to set the
Tom Lane t...@sss.pgh.pa.us wrote:
If you get out of shared memory at all due to SSI, I'd say that
that's the problem, not exactly when it happens. I thought that
the patch included provisions for falling back to coarser-grained
locks whenever it was short of resources.
When one of the
On sön, 2011-04-03 at 16:04 +0200, Magnus Hagander wrote:
The documentation appears to claim that the Platform/Windows SDK without
any Visual Studio should be enough. Is there also an upper limit on the
supported SDK version then?
It certainly used to be enough, so I guess if they have
On Wed, 2011-04-06 at 09:10 +0200, Martijn van Oosterhout wrote:
On Tue, Apr 05, 2011 at 11:55:04PM -0700, Joshua D. Drake wrote:
I want to achieve two things:
1. More understandable .pgpass format. Yes, I understand our standard
format, most people won't. Like JoshB said, hard to debug.
On sön, 2011-04-03 at 12:41 -0400, Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
Well, there isn't any requirement that URIs be
prot://hostname:port/something
They just have to be
prot:something
So you could just turn the existing conninfo syntax into a URI by doing
On Wed, Apr 6, 2011 at 6:27 PM, Peter Eisentraut pete...@gmx.net wrote:
* I have some doubts about whether the SDK is at all needed or
whether it would suffice by itself. I went with Visual Studio
Express 2008.
The SDK is needed with 2008 Express, but not the non-express
On ons, 2011-04-06 at 09:47 -0400, Tom Lane wrote:
Marko Kreen mark...@gmail.com writes:
On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake j...@commandprompt.com
wrote:
1. More understandable .pgpass format. Yes, I understand our standard
format, most people won't. Like JoshB said, hard to
On 04/06/2011 01:34 PM, Dave Page wrote:
On Wed, Apr 6, 2011 at 6:27 PM, Peter Eisentrautpete...@gmx.net wrote:
* I have some doubts about whether the SDK is at all needed or
whether it would suffice by itself. I went with Visual Studio
Express 2008.
The SDK is needed
On Wed, 06 Apr 2011 20:27:22 +0300, Peter Eisentraut
pete...@gmx.net wrote:
I got it to build now. Here are is a list of notes that would make life
easier for future generations:
You might also want to have a look at my VS2010 patch as it already
touches some of those issues.
*
Project Title*: ADJ Dashboard
Name : Erdinc AKKAYA
Email: erdinc.akk...@gmail.com
*Synopsis*
AnyDBJSP is a database monitoring and reporting solution with a browser
based
interface. ADJ dashboard mainly will be written for database admins(DBA).
This tool will have pre-defined sql queries. In
Hello,
O.k., the basic JDBC syntax is:
jdbc:driver://host[:port]/database_name
Where driver is the actual database such as postgresql or db2.
I am thinking something like:
postgres:ssl://localhost:5432/template
Many drivers support an extended syntax like:
Joshua D. Drake j...@commandprompt.com wrote:
Many drivers support an extended syntax like:
postgres:ssl://localhost:5432/template1/?username=jdpassword=foobarssl=true
But I don't know if we want to go there.
We've been there for years:
On ons, 2011-04-06 at 09:51 -0500, Jim Nasby wrote:
Note that doesn't work if the user has superuser because it was granted via
another role.
You can only be a superuser if your own superuser bit is set. It cannot
be granted via some other role. (Not sure whether that's a feature.)
--
On Wed, Apr 06, 2011 at 12:25:26PM -0500, Kevin Grittner wrote:
By the way, the problem with SSI potentially running out of shared
memory is rather parallel to how heavyweight locks can run out of
shared memory. The SLRU prevents the number of transactions from
being limited in that way, and
On Wed, 2011-04-06 at 13:35 -0500, Kevin Grittner wrote:
Joshua D. Drake j...@commandprompt.com wrote:
Many drivers support an extended syntax like:
postgres:ssl://localhost:5432/template1/?username=jdpassword=foobarssl=true
But I don't know if we want to go there.
We've been
On mån, 2011-03-21 at 00:40 +0100, Jan Urbański wrote:
I finally got around to updating the PL/Python tracebacks patch. The
other day I was writing some very simple PL/Python code and the lack of
tracebacks is extremely annoying.
I tweaked this a bit to make the patch less invasive, and then
Hi,
On Wednesday 06 April 2011 20.31:38 Joshua D. Drake wrote:
postgres:ssl://localhost:5432/template1/?username=jdpassword=foobarssl=
true
But I don't know if we want to go there.
I would expect that *if* an URI syntax becomes implemented, it should
support all possible options.
On Wed, 06 Apr 2011 20:04:37 +0200, Brar Piening b...@gmx.de wrote:
It's not ready yet but I'm prepared to get back to it as soon as
there's some serious interest.
I've rebased the patch in case somebody wants to try it.
http://www.piening.info/VS2010v5.patch
Regards,
Brar
--
Sent via
On 06/04/11 21:38, Peter Eisentraut wrote:
On mån, 2011-03-21 at 00:40 +0100, Jan Urbański wrote:
I finally got around to updating the PL/Python tracebacks patch. The
other day I was writing some very simple PL/Python code and the lack of
tracebacks is extremely annoying.
I tweaked this a
On Wed, Apr 6, 2011 at 1:15 PM, aaronenabs aaronen...@btconnect.com wrote:
Wow sounds very complicated. Will have to try that but got to say i am new to
postgresql and might find that difficult. so at the moment i would try and
to the little i can to find parts in the DBMS that can be of use,
Hi,
Does it make sense to treat these ?
ALTER TABLE s'd.s'd.s's'd. ADD COLUMN id bigint DEFAULT
nextval('s''d.s''d.s''d.ds''');
ERROR: improper relation name (too many dotted names): s'd.s'd.s'd.ds'
SQL state: 42601
PostgreSQL 9.1devel on i686-pc-linux-gnu, compiled by GCC gcc
(Ubuntu/Linaro
On Wed, Apr 6, 2011 at 3:27 PM, Dan Ports d...@csail.mit.edu wrote:
On Wed, Apr 06, 2011 at 12:25:26PM -0500, Kevin Grittner wrote:
By the way, the problem with SSI potentially running out of shared
memory is rather parallel to how heavyweight locks can run out of
shared memory. The SLRU
I just spent a rather confused half hour while testing my GUC
assign-hook patch, and when I finally figured out what was happening,
it made me wonder whether we should redesign the behavior a little bit.
The current behavior of ProcessConfigFile is that it runs through all
the name = value pairs
Hi,
A customer of ours has for a long time the desire to be able to return
to the previous privilege level (i.e. the caller privs) inside a
SECURITY DEFINER function. I find that this notion is not at all
covered in the SQL standard, yet the use case is certainly valid from a
security-concious
On Wed, Apr 6, 2011 at 10:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
So I'm thinking we should adopt a strategy that's less likely to result
in divergent behavior among different backends. The idea I have in mind
is to have the first validation pass only check that each name is a
legal GUC
On Wed, Apr 6, 2011 at 5:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I just spent a rather confused half hour while testing my GUC
assign-hook patch, and when I finally figured out what was happening,
it made me wonder whether we should redesign the behavior a little bit.
The current behavior
On 06/04/11 22:16, Jan Urbański wrote:
On 06/04/11 21:38, Peter Eisentraut wrote:
On mån, 2011-03-21 at 00:40 +0100, Jan Urbański wrote:
I finally got around to updating the PL/Python tracebacks patch. The
other day I was writing some very simple PL/Python code and the lack of
tracebacks is
On Apr 6, 2011, at 5:33 PM, Alvaro Herrera wrote:
Hi,
A customer of ours has for a long time the desire to be able to return
to the previous privilege level (i.e. the caller privs) inside a
SECURITY DEFINER function. I find that this notion is not at all
covered in the SQL standard, yet
Robert Haas robertmh...@gmail.com wrote:
The real fix for this problem is probably to have the ability to
actually return memory to the shared pool, rather than having
everyone grab as they need it until there's no more and never give
back. But that's not going to happen in 9.1, so the
I just hit this, which at least violated my sense of least astonishment,
if it's not an outright bug:
After creating a role foo, I added to following lines to my (9.0)
pg_hba.conf:
localall +foo reject
host all +foo 0.0.0.0/0 reject
The surprising (to me)
On Wed, 2011-04-06 at 18:33 -0300, Alvaro Herrera wrote:
(Consider, for example, that you may want to enable a user to run some
operation to which he is authorized, but you want to carry out some
privileged operation before/after doing so: for example, disable
triggers, run an update,
* Andrew Dunstan (and...@dunslane.net) wrote:
The surprising (to me) consequence was that every superuser was
locked out of the system. I had not granted them (or anyone) the
role, but nevertheless these lines took effect.
As I recall, the way we allow superusers to set role to other roles is
I like this proposal. This would bring big benefit to both the
PostgreSQL and the pgpool project.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
Hello
I am sending my proposal about Google Summer Of Code2011.
It would be
On 04/06/2011 01:47 PM, Andrew Dunstan wrote:
On 04/06/2011 01:34 PM, Dave Page wrote:
On Wed, Apr 6, 2011 at 6:27 PM, Peter Eisentrautpete...@gmx.net
wrote:
* I have some doubts about whether the SDK is at all needed or
whether it would suffice by itself. I went with
In my understanding pqc is not designed to be working with pgpool.
Thus if a user want to use both query cache and query dispatching,
replication or failover etc. which are provided by pgpool, it seems
it's not possible. For this purpose maybe user could *cascade* pqc and
pgpool, but I'm not sure.
On Wed, Apr 6, 2011 at 6:32 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Robert Haas robertmh...@gmail.com wrote:
The real fix for this problem is probably to have the ability to
actually return memory to the shared pool, rather than having
everyone grab as they need it until there's
On Wed, Apr 6, 2011 at 7:54 PM, Stephen Frost sfr...@snowman.net wrote:
* Andrew Dunstan (and...@dunslane.net) wrote:
The surprising (to me) consequence was that every superuser was
locked out of the system. I had not granted them (or anyone) the
role, but nevertheless these lines took effect.
If you have the timezone configured to a non-default value in
postgresql.conf, and you comment it out and reload, it says:
LOG: parameter TimeZone removed from configuration file, reset to default
...but at least when I tested it, it didn't actually appear to reset
it to the default.
On Wed, Apr 6, 2011 at 4:23 PM, Vladimir Kokovic
vladimir.koko...@gmail.com wrote:
Hi,
Does it make sense to treat these ?
ALTER TABLE s'd.s'd.s's'd. ADD COLUMN id bigint DEFAULT
nextval('s''d.s''d.s''d.ds''');
ERROR: improper relation name (too many dotted names): s'd.s'd.s'd.ds'
SQL
See bug #5763, and subsequent emails. Short version: Tom argued it
wasn't a bug; Peter and I felt that it was.
Add my vote: it's a bug.
Users who fall afoul of this will spend *hours* trying to debug this
before they stumble on the correct answer. pg_hba.conf is confusing
enough as it is.
Robert Haas robertmh...@gmail.com writes:
On Wed, Apr 6, 2011 at 7:54 PM, Stephen Frost sfr...@snowman.net wrote:
* Andrew Dunstan (and...@dunslane.net) wrote:
The surprising (to me) consequence was that every superuser was
locked out of the system. I had not granted them (or anyone) the
The problem here is that if Andrew had had the opposite case (a
positive-logic hba entry requiring membership in some group to get into
a database), and that had locked out superusers, he'd be on the warpath
about that too. And with a lot more reason.
Actually, I find that behavior
On 04/07/2011 12:29 AM, Tom Lane wrote:
Robert Haasrobertmh...@gmail.com writes:
On Wed, Apr 6, 2011 at 7:54 PM, Stephen Frostsfr...@snowman.net wrote:
* Andrew Dunstan (and...@dunslane.net) wrote:
The surprising (to me) consequence was that every superuser was
locked out of the system. I
Robert Haas robertmh...@gmail.com writes:
If you have the timezone configured to a non-default value in
postgresql.conf, and you comment it out and reload, it says:
LOG: parameter TimeZone removed from configuration file, reset to default
...but at least when I tested it, it didn't actually
75 matches
Mail list logo
