Bruce Momjian wrote:
> I used your suggestion and renamed "online backup" to "incremental
> backup", and added a mention that many database vendors call it
> "online backup".
Consistency would then demand that the other two be renamed to "full
backup". I think we had better suggestions earlier.
I used your suggestion and renamed "online backup" to "incremental
backup", and added a mention that many database vendors call it "online
backup".
Patch attached.
---
Rick Gigger wrote:
> How about:
>
> use "Online backup
Jim C. Nasby wrote:
> If nothing else, this should at least be documented in
> http://www.postgresql.org/docs/8.1/interactive/datatype.html#DATATYPE-SERIAL
I looked at this URL and just didn't see a good place to talk about
SERIAL sequence permissions, so I added something to the GRANT manual
page
Darcy Buskermolen wrote:
On Monday 13 February 2006 14:27, Josh Berkus wrote:
Tom,
And if so, would you mind stopping your mail system from regurgitating
copies of pghackers traffic? It's especially bad that you're sending
the stuff with a fraudulent envelope From, ie, one not pointing back
Tom Lane wrote:
> Bruce Momjian writes:
> > I know we said we don't want to add an additional GUC variable just to
> > control xact statistics, but I am thinking that using
> > stat_command_string isn't a logical variable to use because it is
> > unrelated to commutative statistics.
>
> > I am th
On Monday 13 February 2006 14:27, Josh Berkus wrote:
> Tom,
>
> > And if so, would you mind stopping your mail system from regurgitating
> > copies of pghackers traffic? It's especially bad that you're sending
> > the stuff with a fraudulent envelope From, ie, one not pointing back
> > at yourself
A few days ago, I noticed the following in the postmaster log while
messing with a bug that led to a backend coredump:
[ report of backend sig11, then normal recovery, ending with ]
LOG: transaction ID wrap limit is 1073759685, limited by database "regression"
LOG: invalid server process ID -1
L
Bricklen Anderson <[EMAIL PROTECTED]> writes:
> Where did you see the emails? In this list? I haven't seen any show up
> here, or I would have gotten on this earlier.
No, delivered to me personally, as you can see from the headers. It
just started recently --- I've only gotten two so far.
Tom Lane wrote:
And if so, would you mind stopping your mail system from regurgitating
copies of pghackers traffic? It's especially bad that you're sending
the stuff with a fraudulent envelope From, ie, one not pointing back
at yourself.
That would be me. I've notified one of our admins about
Tom,
> And if so, would you mind stopping your mail system from regurgitating
> copies of pghackers traffic? It's especially bad that you're sending
> the stuff with a fraudulent envelope From, ie, one not pointing back
> at yourself.
The really amusing thing is that presinet.com claim to be "Ne
And if so, would you mind stopping your mail system from regurgitating
copies of pghackers traffic? It's especially bad that you're sending
the stuff with a fraudulent envelope From, ie, one not pointing back
at yourself.
Feb 13 16:55:12 sss2 sm-mta[5221]: k1DLtBSE005221: from=<[EMAIL PROTECTED]>
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Perhaps more to the point: let's do that and wait to see if the field
>> demand justifies expending lots of sweat on anything smarter. Given
>> that we've gone this long with only allowing numeric IPs in pg_hba.conf,
>> I suspect w
So this presents the fact that pg_stattuple should prevent and guess [taking a sample?] that a table needs an urgent lookup instead of ending the scan and presenting real numbers?g.-
On 2/13/06, Chris Browne <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] (Guido Barosio) writes:> quote: " If you are
On 2/13/06, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> Well as one of the people that deploys and managees many, many
> postgresql installations I can say I have never run into the need to
> have dns names and the thought of dns names honestly seems silly. It
> will increase overhead and dependen
On Mon, Feb 13, 2006 at 01:19:46PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > When we build psql with readline, which is our default on many
> > platforms, we are already be GPL'ing psql, at least according to the
> > copyright holders, FSF.
> When we link to a readline library that is no
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Personally, I doubt there's any great use case for DNS names. Like Tom
says, if it involves much more that removing the AI_NUMERICHOST hint
then let's forget it.
Perhaps more to the point: let's do that and wait to see if the field
de
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Personally, I doubt there's any great use case for DNS names. Like Tom
> says, if it involves much more that removing the AI_NUMERICHOST hint
> then let's forget it.
Perhaps more to the point: let's do that and wait to see if the field
demand justifie
Mark Woodward wrote:
Mark Woodward wrote:
If I am a road warrior I want to be able to connect, run my dynamic dns
client, and go.
In your scenario of working as a road warrior, you are almost
certainly not going to be able to have a workable DNS host name unless
you
have a ra
Tom Lane <[EMAIL PROTECTED]> writes:
> > To clearify, I meant the psql binary becomes GPL.
>
> There is no such thing as "the binary becomes GPL". GPL applies to
> the source code.
That's an odd thing to say. The binary is as much covered by copyright as the
source and can't be distributed with
Bruce Momjian writes:
> I know we said we don't want to add an additional GUC variable just to
> control xact statistics, but I am thinking that using
> stat_command_string isn't a logical variable to use because it is
> unrelated to commutative statistics.
> I am thinking using row and block-lev
Tom Lane wrote:
Thomas Hallgren <[EMAIL PROTECTED]> writes:
What I'm proposing should be an addition that also can be seen as the
beginning of a path to migrate the CREATE TYPE construct to conform with
the SQL 2003 standard.
I'd be interested to see where in the SQL2003 spec the synt
> Mark Woodward wrote:
>
>>>If I am a road warrior I want to be able to connect, run my dynamic dns
>>>client, and go.
>>>
>>>
>>>
>>In your scenario of working as a road warrior, you are almost
>>certainly not going to be able to have a workable DNS host name unless
>> you
>>have a raw internet IP
Bruce Momjian wrote:
When we build psql with readline, which is our default on many
platforms, we are already be GPL'ing psql, at least according to the
copyright holders, FSF.
No, we are NOT doing that, not even according to FSF. Our usage of
a pre-installed readline library falls unde
I know we said we don't want to add an additional GUC variable just to
control xact statistics, but I am thinking that using
stat_command_string isn't a logical variable to use because it is
unrelated to commutative statistics.
I am thinking using row and block-level statistics to turn on xact
st
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >>> At that point, psql becomes GPL, no question.
> >>
> >> Which means it's not happening, no?
>
> > To clearify, I meant the psql binary becomes GPL.
>
> There is no such thing as "the binary becomes GPL". GPL applies to
> the sou
Thomas Hallgren <[EMAIL PROTECTED]> writes:
> What I'm proposing should be an addition that also can be seen as the
> beginning of a path to migrate the CREATE TYPE construct to conform with
> the SQL 2003 standard.
I'd be interested to see where in the SQL2003 spec the syntax you are
proposing
I'm not suggesting that we remove the current way of doing things. I
understand that if we did that, it would cause problem for everyone that
has created scalar types up to this day. What I'm proposing is an
alternative way of doing this, not a replacement. And as things stand
today, I'd be hap
Bruce Momjian writes:
> Tom Lane wrote:
>>> At that point, psql becomes GPL, no question.
>>
>> Which means it's not happening, no?
> To clearify, I meant the psql binary becomes GPL.
There is no such thing as "the binary becomes GPL". GPL applies to
the source code.
> When we build psql with
Magnus Hagander wrote:
> > >> What would we patch it with? I don't think anybody has found a
> > >> problem there, this is a separate file that you ship along with it.
> >
> > > Well, the problem is that it handles backslash incorrectly.
> > We could
> > > patch that in the readline source rat
> >> What would we patch it with? I don't think anybody has found a
> >> problem there, this is a separate file that you ship along with it.
>
> > Well, the problem is that it handles backslash incorrectly.
> We could
> > patch that in the readline source rather than playing with a
> > config
Tom Lane wrote:
> Bruce Momjian writes:
> > Magnus Hagander wrote:
> >> What would we patch it with? I don't think anybody has found a problem
> >> there, this is a separate file that you ship along with it.
>
> > Well, the problem is that it handles backslash incorrectly. We could
> > patch tha
Bruce Momjian writes:
> Magnus Hagander wrote:
>> What would we patch it with? I don't think anybody has found a problem
>> there, this is a separate file that you ship along with it.
> Well, the problem is that it handles backslash incorrectly. We could
> patch that in the readline source rathe
Kevin Grittner wrote:
> This patch doesn't leave the standard_conforming_strings entry in guc.c
> with the GUC_REPORT flag, which it needs for psql to work right. Should
> I submit one last patch with this fix and the proper "expected"
> regression file? If so, where should I send it? (The hacke
On Sun, Feb 12, 2006 at 06:29:21PM -0500, Andrew Dunstan wrote:
> Frankly - supplying more sample configs is likely to be fairly
> fruitless. A much better thing would be a really good tuning tool that
> would take stats and logs and other stuff from a running server and
> suggest improvements (
Magnus Hagander wrote:
> > Would the easiest solution be to make a patch to readline for
> > Win32, and only allow Win32 to link to readline if that patch
> > is in readline, and spit out a compile error if readline
> > doesn't have that patch.
>
> What would we patch it with? I don't think any
Just fixed in CVS. Thanks.
---
Dave Page wrote:
> And another failure on Snake
>
> /D
>
> > -Original Message-
> > From: PG Build Farm
> > [mailto:[EMAIL PROTECTED]
> > Sent: 13 February 2006 02:10
> > To: [
Mark Woodward wrote:
If I am a road warrior I want to be able to connect, run my dynamic dns
client, and go.
In your scenario of working as a road warrior, you are almost
certainly not going to be able to have a workable DNS host name unless you
have a raw internet IP address. More than l
Thomas Hallgren <[EMAIL PROTECTED]> writes:
> Ok, so there are two 'optional' arguments. Following my suggestion, the
> input and receive function would always take 3 arguments. Then, it's up
> to the function as such if it makes use of them or not. Do you see any
> problem with that?
(1) backw
>
> If I am a road warrior I want to be able to connect, run my dynamic dns
> client, and go.
>
> HUPing the postmaster every 30 minutes sounds horrible, and won't work
> for what strikes me as the scenario that needs this most. And we surely
> aren't going to build TTL logic into postgres.
>
> I
"Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> I just wanted to check if this has been fixed in any recent v8.1.x
> release, since I'm using v8.1.0 now.
Here's the fix if you need it.
regards, tom lane
Index: allpaths.c
This patch doesn't leave the standard_conforming_strings entry in guc.c
with the GUC_REPORT flag, which it needs for psql to work right. Should
I submit one last patch with this fix and the proper "expected"
regression file? If so, where should I send it? (The hackers list
won't take a file as b
Tom,
Thanks, this was driver error
Dave
On 13-Feb-06, at 9:26 AM, Tom Lane wrote:
Dave Cramer <[EMAIL PROTECTED]> writes:
I am confused, I thought that there were only supposed to be links to
the actual data in pg_tblspc ?
I have a db defined in a tablspace, but in pg_tblspc there is 1
[EMAIL PROTECTED] writes:
> On Mon, Feb 13, 2006 at 10:00:34AM -0500, Andrew Dunstan wrote:
>> We can over-egg this pudding massively. I suggest we start with a simple
>> implementation and see what needs it leaves unfilled. I would vote for
>> allowing a hostname (or list of hostnames?) to repla
On Mon, Feb 13, 2006 at 10:00:34AM -0500, Andrew Dunstan wrote:
> Mark Woodward wrote:
> >I'm not so sure you need to be paranoid about it. The scenario is, at
> >startup or HUP, names are looked up and stored as IP addresses. Then hba
> >works as it is supposed too.
> If you do it like that you de
Tom Lane wrote:
> "Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
>> SELECT DISTINCT
>> *
>> FROM
>> (
>> SELECT
>> vtgm.snicker_id
>> FROM snicker_group_mapping vtgm
>> WHERE exists
>> (
>> SELECT
>> *
>> FROM snicker_group vtg
>>
Mark Woodward wrote:
Mark Woodward wrote:
Added to TODO:
o Allow pg_hba.conf to specify host names along with IP
addresses
Host name lookup could occur when the postmaster reads the
pg_hba.conf file, or when the backend starts. Another
solution would be to
> Mark Woodward wrote:
>
>>>Added to TODO:
>>>
>>>o Allow pg_hba.conf to specify host names along with IP
>>> addresses
>>>
>>> Host name lookup could occur when the postmaster reads the
>>> pg_hba.conf file, or when the backend starts. Another
>>> solution would
Mark Woodward wrote:
Added to TODO:
o Allow pg_hba.conf to specify host names along with IP addresses
Host name lookup could occur when the postmaster reads the
pg_hba.conf file, or when the backend starts. Another
solution would be to reverse lookup the conn
"Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> SELECT DISTINCT
> *
> FROM
> (
> SELECT
> vtgm.snicker_id
> FROM snicker_group_mapping vtgm
> WHERE exists
> (
> SELECT
> *
> FROM snicker_group vtg
> WHERE vtgm.snicker_group_
Dave Cramer <[EMAIL PROTECTED]> writes:
> I am confused, I thought that there were only supposed to be links to
> the actual data in pg_tblspc ?
> I have a db defined in a tablspace, but in pg_tblspc there is 1.2G of
> data corrresponding to it?
Are you on a system that has symlinks? Are you
I just wanted to check if this has been fixed in any recent v8.1.x
release, since I'm using v8.1.0 now.
Backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x08152448 in qual_is_pushdown_safe ()
(gdb) bt
#0 0x08152448 in qual_is_pushdown_safe ()
#1 0x08151e47 in set_subquery_pathlis
Hello,
That's caused by small error in recent implementation of dealing with
multi-line queries.
I already have sent the patch to pgsql-patches
Regards,
Sergey
On Mon, 13 Feb 2006, Dave Page wrote:
> And another failure on Snake
>
> /D
>
> > -Original Message-
> > From:
>
> Added to TODO:
>
> o Allow pg_hba.conf to specify host names along with IP addresses
>
> Host name lookup could occur when the postmaster reads the
> pg_hba.conf file, or when the backend starts. Another
> solution would be to reverse lookup the connection
I am confused, I thought that there were only supposed to be links to
the actual data in pg_tblspc ?
I have a db defined in a tablspace, but in pg_tblspc there is 1.2G of
data corrresponding to it?
Dave
---(end of broadcast)---
TIP 5: don't f
> Would the easiest solution be to make a patch to readline for
> Win32, and only allow Win32 to link to readline if that patch
> is in readline, and spit out a compile error if readline
> doesn't have that patch.
What would we patch it with? I don't think anybody has found a problem
there, thi
And another failure on Snake
/D
> -Original Message-
> From: PG Build Farm
> [mailto:[EMAIL PROTECTED]
> Sent: 13 February 2006 02:10
> To: [EMAIL PROTECTED]
> Subject: PGBuildfarm member snake Branch HEAD Status changed
> from CVS-Unknown failure to Make failure
>
>
> The PGBuil
how? is there some kernel patch to completely to enable you to deny
access to root?
Tino Wildenhain pointed out SELinux has a feature like that.
I still dont get your problem (apart from that you can always
google for SELinux)
Why arent the other "admins" not trustworthy? And why do you
have ma
Q Beukes schrieb:
how? is there some kernel patch to completely to enable you to deny
access to root?
Tino Wildenhain pointed out SELinux has a feature like that.
I still dont get your problem (apart from that you can always
google for SELinux)
Why arent the other "admins" not trustworthy? And
how? is there some kernel patch to completely to enable you to deny
access to root?
Tino Wildenhain pointed out SELinux has a feature like that.
Rick Gigger wrote:
> But why do they need access to the files in the file system? Why not
> put them on the local box but don't give them permissions
59 matches
Mail list logo
