Bruce Momjian wrote:
KaiGai Kohei wrote:
Bruce Momjian wrote:
KaiGai Kohei wrote:
Please consider SELinux/SE-PostgreSQL requires various kind of objects
(including database objects) to be labeled properly at the initial state.
If it allows clients to turn on row-level security feature, it mean
2008/11/22 Heikki Linnakangas <[EMAIL PROTECTED]>:
> Just to let you know, I'm hacking this patch again, the executor part in
> particular. I've got a stripped out the unfinished window frame stuff,
> refactored the Window object API so that the window functions don't get to,
> and don't need to, a
Just to let you know, I'm hacking this patch again, the executor part in
particular. I've got a stripped out the unfinished window frame stuff,
refactored the Window object API so that the window functions don't get
to, and don't need to, access tuple slots directly. And a bunch of other
simpli
Sorry for the late response; I was on vacation.
>>> Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
> Kevin, what was your original scenario like that led you to
investigate
> this?
We noticed a performance degradation in application code which, within
a database transaction, looped through lar
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > Or in the same directly, called something else. Like fnmatchstub.h. See
> > attached, seems reasonable?
>
> Seems okay to me. Note: in future, don't bother posting configure
> diffs; nobody wants to look at that, just the changes i
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> ... the file
>> that is actually being delivered in snapshots still contains man1/
>> and manl/. So that file needs to be regenerated. Peter?
> Shouldn't it be part of the nightly snapshot creation to make that file?
> In the snaps
Alvaro Herrera wrote:
> David Fetter escribi?:
> > On Fri, Nov 21, 2008 at 04:11:11PM -0500, Tom Lane wrote:
>
> > > This is a cool hack, agreed, but that doesn't make it a useful
> > > regression test. Whatever value it might have isn't going to repay
> > > the community-wide expenditure of cycl
David Fetter escribió:
> On Fri, Nov 21, 2008 at 04:11:11PM -0500, Tom Lane wrote:
> > This is a cool hack, agreed, but that doesn't make it a useful
> > regression test. Whatever value it might have isn't going to repay
> > the community-wide expenditure of cycles.
>
> What's the slowest it run
On Fri, Nov 21, 2008 at 04:11:11PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Fri, Nov 21, 2008 at 09:06:13PM +0100, Zdenek Kotala wrote:
> >> I takes 2.6 second on my laptop. I think it is not so bad.
>
> > About 2.0 on my OS/X laptop. Could this be a problem on wha
Tom Lane wrote:
It looks to me like the problem is that the makefile expects the
man.tar.gz file to contain stuff in man1/ and man7/, but the file
that is actually being delivered in snapshots still contains man1/
and manl/. So that file needs to be regenerated. Peter?
David Fetter <[EMAIL PROTECTED]> writes:
> On Fri, Nov 21, 2008 at 09:06:13PM +0100, Zdenek Kotala wrote:
>> I takes 2.6 second on my laptop. I think it is not so bad.
> About 2.0 on my OS/X laptop. Could this be a problem on whatever
> architecture/OS/compiler combo you have?
Not everyone is us
On Fri, Nov 21, 2008 at 09:06:13PM +0100, Zdenek Kotala wrote:
> Alvaro Herrera napsal(a):
>> David Fetter escribió:
>>> On Wed, Nov 19, 2008 at 10:21:06PM -, David Rowley wrote:
Gregory Stark wrote:
> So based on Graeme Job's T-SQL hack over at thedailywtf.com I
> adapted the T-SQ
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Jaime Casanova wrote:
>> i saw the same on a nightly snapshot a week ago, then used cvs and
>> everything was good... i thouhgt it was a problem already solved...
>> could be a problem in the nightly builds?
> Yeah. Buildfarm doesn't do docs at all.
>
On Fri, Nov 21, 2008 at 3:06 PM, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
>
> I takes 2.6 second on my laptop. I think it is not so bad.
>
Time: 694.512 ms
:-)
merlin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgres
Jaime Casanova wrote:
On Thu, Nov 20, 2008 at 4:31 AM, ITAGAKI Takahiro
<[EMAIL PROTECTED]> wrote:
I used a nightly snapshot(snapshot/postgresql-snapshot.tar.bz2)
and it includes *.gz files. It would be the cause.
i saw the same on a nightly snapshot a week ago, then used cvs and
ev
Alvaro Herrera napsal(a):
David Fetter escribió:
On Wed, Nov 19, 2008 at 10:21:06PM -, David Rowley wrote:
Gregory Stark wrote:
So based on Graeme Job's T-SQL hack over at thedailywtf.com I adapted the
T-SQL code to Postgres and got this. Thought others might find it amusing.
That's pret
Robert Haas escribió:
> >> Maybe syslog?
> >
> > Doesn't exist on Windows ...
>
> There is an event log though which is fairly comparable. Of course
> that still leaves you with the problem of what to do when the syslog
> or event log write fails.
Well, syslog does not have a return code, which
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Last I checked, Magnus had promised to come up with suitable
>>> documentation changes for this patch, but then he went off sailing...
>
>> Meh, I seem to have forgotten this one again. Here's a suggestion, seems
Greg Stark <[EMAIL PROTECTED]> writes:
> If you want people to stop posting configure diffs you should remove
> the damn configure file from CVS where it doesn't belong.
Well, that'd require everyone using CVS to have autoconf installed
--- and not just any autoconf, but the specific version. S
If you want people to stop posting configure diffs you should remove
the damn configure file from CVS where it doesn't belong.
greg
On 21 Nov 2008, at 06:49 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
Magnus Hagander <[EMAIL PROTECTED]> writes:
Or in the same directly, called something else. Lik
On Thu, Nov 20, 2008 at 4:31 AM, ITAGAKI Takahiro
<[EMAIL PROTECTED]> wrote:
>
> I used a nightly snapshot(snapshot/postgresql-snapshot.tar.bz2)
> and it includes *.gz files. It would be the cause.
>
i saw the same on a nightly snapshot a week ago, then used cvs and
everything was good... i thouhg
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Or in the same directly, called something else. Like fnmatchstub.h. See
>> attached, seems reasonable?
>
> Seems okay to me. Note: in future, don't bother posting configure
> diffs; nobody wants to look at that, just the changes in
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Also, the output datatype should be text[] not cstring[].
>
>> Ok, will change. That requires hardcode of 1009? Or should I a #define
>> to pg_type.h?
>
> Add a #define (bit surprising we didn't have one already)
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Or in the same directly, called something else. Like fnmatchstub.h. See
> attached, seems reasonable?
Seems okay to me. Note: in future, don't bother posting configure
diffs; nobody wants to look at that, just the changes in the autoconf
input files.
Hi, Simon. Thanks for the comment!!
On Sat, Nov 22, 2008 at 2:09 AM, Simon Riggs <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2008-11-20 at 22:41 +0900, Fujii Masao wrote:
>
>> In the current Synch Rep patch, the standby cannot catch up with the
>> primary which has a bigger timeline. So, whenever makin
>> Maybe syslog?
>
> Doesn't exist on Windows ...
There is an event log though which is fairly comparable. Of course
that still leaves you with the problem of what to do when the syslog
or event log write fails.
...Robert
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Also, the output datatype should be text[] not cstring[].
> Ok, will change. That requires hardcode of 1009? Or should I a #define
> to pg_type.h?
Add a #define (bit surprising we didn't have one already)
re
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> The attached patch changes pg_settings.enumval to be an array of text
>> instead of just a string, per previous discussion and the open items list.
>
>> Comments?
>
> Hmmm ... this coding will fail if any enumval contains a double q
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Last I checked, Magnus had promised to come up with suitable
>> documentation changes for this patch, but then he went off sailing...
> Meh, I seem to have forgotten this one again. Here's a suggestion, seems
> ok, or were you thinki
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> I was writing a simple standalone function compiled with pgxs - been a
>> while since I did that.
>
>> Including "postgres.h" and "fmgr.h", it didn't work - the backend would
>> complain that the function did not exist in the shared
Magnus Hagander <[EMAIL PROTECTED]> writes:
> The attached patch changes pg_settings.enumval to be an array of text
> instead of just a string, per previous discussion and the open items list.
> Comments?
Hmmm ... this coding will fail if any enumval contains a double quote.
Which is probably not
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I didn't say it was --- merely opined that we need a consistent plan
>> about how to handle corner cases like that if we want to try to wipe out
>> all the warnings of this class.
> Maybe syslog?
Doesn't exist on Windows ...
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> (Whatcha gonna do if you fail to write the postmaster log ... try to
> >> log a complaint message?)
>
> > Well, good question, but I'm not convinced that doing nothing is always
> > the best answer.
>
> I did
Alvaro Herrera wrote:
> Magnus Hagander escribió:
>> Alex Hunsaker wrote:
>>> On Fri, Aug 1, 2008 at 13:31, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Something that's bothering me is that PGSSLKEY is inconsistent with the
sslkey conninfo parameter. PGSSLKEY specifies an engine (basically
On Thu, 2008-11-20 at 22:41 +0900, Fujii Masao wrote:
> In the current Synch Rep patch, the standby cannot catch up with the
> primary which has a bigger timeline. So, whenever making the standby
> catch up, a fresh base backup is required. This is obviously undesirable,
> and I'd like to get rid
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> (Whatcha gonna do if you fail to write the postmaster log ... try to
>> log a complaint message?)
> Well, good question, but I'm not convinced that doing nothing is always
> the best answer.
I didn't say it was --- merely opined t
On Fri, 2008-11-21 at 15:45 +1100, Philip Warner wrote:
> Sounds somewhat evil, I know, but I was wondering if it was even
> remotely possible with the current design?
>
> The reason: we are contemplating using pg_standy to create a
> warm-standby. It would be a bonus if we would run read-only qu
Tom Lane wrote:
(Whatcha gonna do if you fail to write the postmaster log ... try to
log a complaint message?)
Well, good question, but I'm not convinced that doing nothing is always
the best answer. Something along the lines of SIGSTOP'ing oneself or
calling abort() might be appropriate in
Magnus Hagander <[EMAIL PROTECTED]> writes:
> I was writing a simple standalone function compiled with pgxs - been a
> while since I did that.
> Including "postgres.h" and "fmgr.h", it didn't work - the backend would
> complain that the function did not exist in the shared library.
> Including "po
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> relation_expr is fine by me. It just makes the syntax more complicated
> to explain ...
> Btw., so we plan to keep the sql_inheritance parameter forever?
I have no idea ... but I should think we'd want to allow ONLY here in
any case. You can use t
Heikki Linnakangas wrote:
Emmanuel Cecchet wrote:
I still quite did not get what the big deal was if an ON COMMIT
DELETE ROWS temp table was created inside a transaction.
In case the transaction that created a temp table rolls back, the
table needs to be removed. Removing a temporary table be
I was writing a simple standalone function compiled with pgxs - been a
while since I did that.
Including "postgres.h" and "fmgr.h", it didn't work - the backend would
complain that the function did not exist in the shared library.
Including "postgres.h" and "funcapi.h" *did* work - no complaints.
KaiGai Kohei wrote:
> Bruce Momjian wrote:
> > KaiGai Kohei wrote:
> Please consider SELinux/SE-PostgreSQL requires various kind of objects
> (including database objects) to be labeled properly at the initial state.
> If it allows clients to turn on row-level security feature, it mea
Magnus Hagander escribió:
> Alex Hunsaker wrote:
> > On Fri, Aug 1, 2008 at 13:31, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> >> Something that's bothering me is that PGSSLKEY is inconsistent with the
> >> sslkey conninfo parameter. PGSSLKEY specifies an engine (basically a
> >> driver for specia
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> AFAICS, we're not doing this for any other functions though - or am I
>> too tired and just looking in the wrong place? Or is that because
>> they're just function definitions and not #defines?
>> (I want to be sure to stick whatever
On Fri, 2008-11-21 at 15:21 +0530, Pavan Deolasee wrote:
>
> + /*
> +* Release locks, if any.
> +*/
> + RelationReleaseRecoveryLocks(xlrec->slotId);
>
>
> If I am reading the patch correctly, AccessExclusiveLocks acquired by
> a transaction will be released when the
Alex Hunsaker wrote:
> On Fri, Aug 1, 2008 at 13:31, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>> Something that's bothering me is that PGSSLKEY is inconsistent with the
>> sslkey conninfo parameter. PGSSLKEY specifies an engine (basically a
>> driver for specialized hardware AFAICT) from which th
On Fri, 2008-11-21 at 13:22 +0530, Pavan Deolasee wrote:
>
> I think we should avoid the #define's like below which uses a local
> variable. I guess the same #define is used elsewhere in the code as
> well. If the code is rearranged or the variable name is changed, the
> code would break.
I use
On Fri, 2008-11-21 at 17:08 +0530, Pavan Deolasee wrote:
> Sorry, its the startup process thats stuck in the checkpoint. Here is
> the stack trace:
Already fixed in new version I'm preparing for you.
Both the startup process and bgwriter can perform restartpoints, so its
not a problem whether w
The attached patch changes pg_settings.enumval to be an array of text
instead of just a string, per previous discussion and the open items list.
Comments?
//Magnus
*** a/src/backend/utils/misc/guc.c
--- b/src/backend/utils/misc/guc.c
***
*** 168,174 static bool assign_maxconnecti
On Thu, Nov 20, 2008 at 8:15 PM, Pavan Deolasee <[EMAIL PROTECTED]>wrote:
>
>
> On Thu, Nov 20, 2008 at 7:50 PM, Simon Riggs <[EMAIL PROTECTED]>wrote:
>
>
>
>>
>> (I assume you mean bgwriter, not archiver process).
>>
>>
> Yeah, its the bgwriter, IIRC hung while taking checkpoint.
>
>
>
Sorry, its
Tom Lane wrote:
[EMAIL PROTECTED] (Peter Eisentraut) writes:
Log Message:
---
TABLE command
If this got re-posted for review I missed it :-(. I disagree with using
qualified_name here --- I think it would be better to use relation_expr
so that people would have the ability to specify
Bruce Momjian wrote:
KaiGai Kohei wrote:
Please consider SELinux/SE-PostgreSQL requires various kind of objects
(including database objects) to be labeled properly at the initial state.
If it allows clients to turn on row-level security feature, it means many
"unlabeled" tuples appear suddenly.
+ /*
+* Release locks, if any.
+*/
+ RelationReleaseRecoveryLocks(xlrec->slotId);
If I am reading the patch correctly, AccessExclusiveLocks acquired by a
transaction will be released when the transaction is committed or aborted.
If the transaction errors out with FATAL
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>> bruce wrote:
>>> Tom Lane wrote:
Currently, config.sgml still describes the new "enum" GUC variables
as being of type "string" --- but pg_settings says they are "enum".
This is not very consistent, but I wonder whether ch
I wonder if there is corner case below where there are no WAL records to
replay during standby recovery. Specifically, that may cause
IsRunningXactDataValid() to return false since latestObservedXid remains set
to InvalidTransactionId and that prevents postmaster from serving read-only
clients.
I
56 matches
Mail list logo
