Brendan Jurd writes:
> TRAP: FailedAssertion("!((data - start) == data_size)", File:
> "heaptuple.c", Line: 255)
[ scratches head ... ] That implies that heap_fill_tuple came to a
different conclusion about a tuple's data size than the immediately
preceding heap_compute_data_size. Which I would
On 4/7/11, Robert Haas wrote:
> On Wed, Apr 6, 2011 at 4:23 PM, Vladimir Kokovic
> 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".d"s''"');
>>
>> ERROR: improper relation name (too ma
On 04/05/2011 02:21 PM, Mischa Sandberg 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.
Only a little old;
http://postgresq
Hi folks,
I am running a 9.0.3 Hot Standy + Streaming Replication slave which
occasionally segfaults (every 1-2 days). I rebuilt Postgres with
--enable-cassert and --enable-debug, switched on core dumping and
waited for some results.
The first crash since enabling debugging was a failed assert i
Robert Haas 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 appear to reset
On 04/07/2011 12:29 AM, Tom Lane wrote:
Robert Haas writes:
On Wed, Apr 6, 2011 at 7:54 PM, Stephen Frost 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
ro
> 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 surpr
Robert Haas writes:
> On Wed, Apr 6, 2011 at 7:54 PM, Stephen Frost 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 lin
> 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.
On Wed, Apr 6, 2011 at 4:23 PM, Vladimir Kokovic
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".d"s''"');
>
> ERROR: improper relation name (too many dotted names): s'd.s'd"".s'd.d"s'"
> SQL
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.
assign_t
On Wed, Apr 6, 2011 at 7:54 PM, Stephen Frost 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.
>
> As I re
On Wed, Apr 6, 2011 at 6:32 PM, Kevin Grittner
wrote:
> Robert Haas 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
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 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 Eisentraut
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
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 b
* 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 i
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, re-en
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) consequenc
Robert Haas 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 question is
> whether t
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,
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
>>> trac
On Wed, Apr 6, 2011 at 5:17 PM, Tom Lane 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 of ProcessConfi
On Wed, Apr 6, 2011 at 10:17 PM, Tom Lane 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 variable name, a
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 po
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
On Wed, Apr 6, 2011 at 3:27 PM, Dan Ports 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 prevents the num
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".d"s''"');
ERROR: improper relation name (too many dotted names): s'd.s'd"".s'd.d"s'"
SQL state: 42601
PostgreSQL 9.1devel on i686-pc-linux-gnu, compiled by GCC
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
On Wed, 06 Apr 2011 20:04:37 +0200, Brar Piening 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 pgsql-hackers
Hi,
On Wednesday 06 April 2011 20.31:38 Joshua D. Drake wrote:
> postgres:ssl://localhost:5432/template1/?username=jd&password=foobar&ssl=
> 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.
Esp
On Wed, Apr 6, 2011 at 1:15 PM, aaronenabs 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, as i
> already tried st
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
On Wed, 2011-04-06 at 13:35 -0500, Kevin Grittner wrote:
> "Joshua D. Drake" wrote:
>
> > Many drivers support an extended syntax like:
> >
> >
> postgres:ssl://localhost:5432/template1/?username=jd&password=foobar&ssl=true
> >
> > But I don't know if we want to go there.
>
> We've been ther
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, a
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.)
--
Se
"Joshua D. Drake" wrote:
> Many drivers support an extended syntax like:
>
>
postgres:ssl://localhost:5432/template1/?username=jd&password=foobar&ssl=true
>
> But I don't know if we want to go there.
We've been there for years:
http://jdbc.postgresql.org/documentation/head/connect.html
-
Hello,
O.k., the basic JDBC syntax is:
jdbc:://[:]/
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:
postgres:ssl://localhost:5432/template1/?username=jd&password
*
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 ad
On Wed, 06 Apr 2011 20:27:22 +0300, Peter Eisentraut
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.
https://commitfest.postgresq
On 04/06/2011 01:34 PM, Dave Page wrote:
On Wed, Apr 6, 2011 at 6:27 PM, Peter Eisentraut 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 Expre
On ons, 2011-04-06 at 09:47 -0400, Tom Lane wrote:
> Marko Kreen writes:
> > On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake
> > wrote:
> >> 1. More understandable .pgpass format. Yes, I understand our standard
> >> format, most people won't. Like JoshB said, hard to debug.
>
> > How about allo
On Wed, Apr 6, 2011 at 6:27 PM, Peter Eisentraut 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 version.
The
On sön, 2011-04-03 at 12:41 -0400, Tom Lane wrote:
> Peter Eisentraut 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, 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 t
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
Tom Lane 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 tests was getti
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
HeapTuplevisiblit
Heikki Linnakangas 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 claimed by
>> whichever table uses
Robert Haas writes:
> On Wed, Apr 6, 2011 at 11:13 AM, aaronenabs 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(
On 6 April 2011 17:57, Heikki Linnakangas
wrote:
> On 06.04.2011 17:46, Tom Lane wrote:
>>
>> "Kevin Grittner" writes:
>>>
>>> Robert Haas 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 n
On 06.04.2011 17:46, Tom Lane wrote:
"Kevin Grittner" writes:
Robert Haas 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 with it.
"Kevin Grittner" writes:
> Robert Haas 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 with it.
> I haven't seen any obje
Robert Haas wrote:
> Heikki Linnakangas 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
>> pretty complicated code to review.
>
> I'll try,
On Wed, Apr 6, 2011 at 12:06 PM, Heikki Linnakangas
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 who is going to pick all t
On 06.04.2011 18:02, Tom Lane wrote:
Robert Haas 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 colla
On Tue, Apr 05, 2011 at 09:44:44AM -0400, Robert Haas wrote:
> On Wed, Mar 30, 2011 at 9:32 PM, Noah Misch 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 uses each c
On Wed, Apr 6, 2011 at 11:13 AM, aaronenabs 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, snapshot, buffer)(1)
We
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:
http://postgresql.1045698.n
Robert Haas 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 done with that
bef
On Wed, Apr 6, 2011 at 9:48 AM, aaronenabs 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 there are hidden xmin an
On Wed, Apr 6, 2011 at 9:42 AM, Tom Lane wrote:
> Robert Haas 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
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
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 m
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:
http://postgresql.1045698.n5.nabble.com/Transaction-log-tp4285471p4286318.ht
Marko Kreen writes:
> On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake
> 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 putting field
> list into all templat
Robert Haas 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 those areas and
On Tue, Apr 5, 2011 at 2:21 PM, Mischa Sandberg
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.
>
> The group at MIT were
On Wed, Apr 6, 2011 at 6:49 AM, aaronenabs 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 viewing
> it.
That's pret
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 col
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 you'
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 sever
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, m
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" wrote:
> Hello
>
> My name is Masanori Yamazaki. I am sending my proposal about
> Google Summe
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:
http://postgresql.1045698.n5.nabble.
On Wed, Apr 6, 2011 at 9:55 AM, 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.
How about allowing '#'-comments there and putting field
list into all templ
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
77 matches
Mail list logo
