be improved, but the
second sentence ("This privilege is also needed..") is intended to cover
the case where the column is being referred to *anywhere* in the query,
basically, and that applies to SELECT as much as UPDATE or DELETE.
Thanks,
Stephen
signature.asc
Description: Digital signature
* Pawel Kozik (pawel.ko...@alcatel-lucent.com) wrote:
> Any idea when it will be available in official PostgreSQL release 9.1.x or
> 9.2.x ?
Yes, the next set of point releases should include Tom's patch to fix
this leak.
Thanks,
Stephen
signature.asc
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> I'm already working on back-patching the attached.
Works for me,
Thanks!
Stephen
signature.asc
Description: Digital signature
dbySnapshot?
Certainly good questions and better comments would have helped here. I
can go back and rework the patch either way.
Thanks,
Stephen
signature.asc
Description: Digital signature
uses a
static variable to keep track of memory allocated for the data being
returned to the caller.
Looks like this will need to be back-patched to 9.0. Barring objections
or better ideas, I'll do that in a few hours.
Thanks,
Stephen
colordiff --git a/src/backend/s
ne with fixing it either way.
And this is really the other point- having LogStandbySnapshot() need to
clean up after GetRunningTransactionLocks() but not
GetRunningTransactionData() would strike me as very odd.
Thanks,
Stephen
signature.asc
Description: Digital signature
reuse the same memory, ala what GetRunningTransactionData() does, and
avoid having to do allocation while holding all the locks (or at least,
not very often).
Thanks,
Stephen
signature.asc
Description: Digital signature
t; changing the structure name to Extension does not look to be appropriate as
> it is a generic name...
Took a simpler approach and just renamed it to CoverExt, that should
also avoid any confusion with actual extensions.
Thanks,
Stephen
signature.asc
Description: Digital signature
R TYPE .. RENAME ATTRIBUTE and that it isn't supported
for ALTER TYPE .. RENAME TO. This update will be pushed out with the
next releases.
Thanks!
Stephen
signature.asc
Description: Digital signature
ly. I agree that it's
a documentation issue. Of course, that makes it easier to fix. :)
Thanks,
Stephen
signature.asc
Description: Digital signature
Maxim,
* Stephen Frost (sfr...@snowman.net) wrote:
> * maxim.bo...@gmail.com (maxim.bo...@gmail.com) wrote:
> > It seems that documentation wrong or [ CASCADE | RESTRICT ] feature of ALTER
> > TYPE ... RENAME TO isn't implemented.
>
> Actually, I'm pretty sure i
oring to have all the ALTER .. RENAME operations go
through the same code paths.
> Test case:
Thanks for this. I'm working on fixing this and will also add
regression tests to, hopefully, avoid this getting broken in the future.
Thanks again,
Stephen
signa
rows cannot return null value
=> select * from unnest(array[row(null)::xt]);
a
---
(1 row)
Thanks,
Stephen
signature.asc
Description: Digital signature
ich adhere to it, if there's someone willing to do the
work to fix it.
I'm not volunteering (yet), but I wouldn't say "no, we're never going to
fix this" either. Perhaps a TODO item to investigate the value of
making relname variable length? Or to investigate the actual impact of
increasing the length?
Thanks,
Stephen
signature.asc
Description: Digital signature
his to be an
ERROR in 9.3. I don't see the value in the truncation and feel it's
actually dangerous, particularly if ORMs are doing things like this.
Thanks,
Stephen
signature.asc
Description: Digital signature
Hi I am created a function
CREATE FUNCTION one(float,float) RETURNS float AS $$
select $1+$2 AS result;
$$ LANGUAGE SQL;
Its worked
Then
I droped the function
Drop function one(float,float)
Its also worked
Then I typed
Select one(18.5,12.4)
Ho… the result appers as 31.9
The following bug has been logged online:
Bug reference: 6255
Logged by: stephen
Email address: snpmons...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Windows 7
Description:Unable to Install (Binary, One Click Installer
Details:
Hi,
I tried installing
tion, I don't see
any reason why we should be allowing it in to_timestamp(). If the
values at the 'MM' location are outside of the valid range, we should be
throwing an error.
Thanks,
Stephen
signature.asc
Description: Digital signature
RAM...).
Thanks,
Stephen
signature.asc
Description: Digital signature
's a whole lot of rather complex work though.
Thanks,
Stephen
signature.asc
Description: Digital signature
x it to use hostaddr if host is null.
That's fine with me. I'd rather have it not broken anyway.
Thanks,
Stephen
signature.asc
Description: Digital signature
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > Perhaps I was being a bit overzealous in my last response, sorry about
> > that. If the point here is that people who are using hostaddr are in an
> > environment where DNS is non-functional or actively broke
blis.org
I always get a postgres/beren.tsf.noblis@tsf.noblis.org ticket, for
that server, since that's what the rDNS is, and that's what's in the KDC
(it hasn't got entries for any of the others).
In any case, let's please make sure not to break that. :)
Thanks!
Stephen
signature.asc
Description: Digital signature
7;t break without
a real reason.
Thanks,
Stephen
signature.asc
Description: Digital signature
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > krb5_sname_to_principal() will use the passed hostname for the second
> > component. If type is KRB5_NT_SRV_HST this name will be looked up with
> > gethostbyname(). If hostname is NULL, the l
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > I've never found a reason to use hostaddr, so I don't particularly care,
> > but it doesn't seem right to break Kerberos auth if you were only given
> > an IP address unless hostaddr'
m right to break Kerberos auth if you were only given
an IP address unless hostaddr's entire point is that it will prevent a
DNS lookup from happening, ever. If that's the case, it should probably
be made more clear in the docs that you can't use hostaddr w/ Kerberos
but
works in the
libpq documentation or what the context is for the above, but I'm pretty
sure that's where the original wording came from.
Thanks,
Stephen
signature.asc
Description: Digital signature
ional switch
> "--data-file=filename", with the schema output still going where it
> goes now (ie, -f or stdout).
+1 from me, excellent solution.
Thanks,
Stephen
signature.asc
Description: Digital signature
hings. Easier to find than searching the archive,
ime. Of course, that'll probably change as more things get added to the
wiki. :)
Thanks,
Stephen
signature.asc
Description: Digital signature
' option with a 'base-file-name'
parameter which then generates:
pre-data DDL
data
post-data DDL
psql script to run them in order (\i-style)
?
Just my 2c.
Thanks,
Stephen
signature.asc
Description: Digital signature
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > Erm, I don't know that we deal with function-body problems today, even
> > when using the newer version of pg_dump, do we?
>
> Right, any forward-compatibility problems arising inside functions
> ar
to run the function? We use $ quoting for the function bodies
entirely otherwise...
Thanks,
Stephen
signature.asc
Description: Digital signature
what has to be *quoted* inside a quoted identifier terribly
often...
Thanks,
Stephen
signature.asc
Description: Digital signature
to it w/o code duplication, that'd be great, but it just
doesn't feel like a hard problem to solve or one that requires a huge
amount of code..
Thanks,
Stephen
signature.asc
Description: Digital signature
are and
fix them". Obviously, we should caveat our response that this will only
fix the pg_dump/restore problem and that their applications may need to
be fixed.
Thanks,
Stephen
signature.asc
Description: Digital signature
realize there's an issue, but then
have a way to actually *fix* the restore without having to hack up
multi-gigabyte files using vi. If you'd like, you're welcome to
consider the default of "off" as a feature.
+1 from me for adding the option.
Thanks,
Stephen
signature.asc
Description: Digital signature
* Hartmut Goebel (h.goe...@goebel-consult.de) wrote:
> Am 04.06.2010 13:56, schrieb Stephen Frost:
> > Quoting all column names makes the dump script much more difficult for
> > human consumption, which is important.
>
> I don't agree with you here. But this may be
eadability for humans is important.
> So if readability is not important, what speaks against always quoting
> the column names?
Quoting all column names makes the dump script much more difficult for
human consumption, which is important.
Thanks,
Stephen
--
Sent
how I did it the other
> day (hence why I've only just got the error today).
public is in your search_path by default- that's why it works. Still,
it's not really a *good* approach. Use the one that Tom showed.
Thanks,
Stephen
signature.asc
Description: Digital signature
since
they can change over time and make things more difficult.).
> > In any case I'm thinking that we need to document how to set up
> > configurations with chains of CA certs.
>
> Yes, and patch the server to send the list of trusted CAs to the client
> during client certificate negotiaton to fix #5468 .
Agreed.
Thanks,
Stephen
signature.asc
Description: Digital signature
confusion about intermediate CAs being accepted as root CAs just because
they're in the same file or directory.
All that being said- I don't think anyone would really complain if
intermediate CAs and root CAs were stored in different
directories/files. That's how Windows ha
utils/2006-09/threads.html#00359
And the first annoucement of the complete rewrite of remove.c is here:
http://lists.gnu.org/archive/html/bug-coreutils/2009-08/msg00295.html
Stephen Tyler
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
-f is set to stdin..
Thanks,
Stephen
signature.asc
Description: Digital signature
.
> I kinda thought we *had* been doing that, but can't claim to have read
> that code closely. Magnus?
We should certainly either be requiring the princ match the user in the
database, or that it is allowed through a username mapping where a
mapping table has been supplied, ala ident.
Stephen
signature.asc
Description: Digital signature
nd
ca-certificates and default config the client to use those. Of course,
anyone who actually cares about security probably wouldn't install
ca-certificates, but it's what the browsers use.
Thanks,
Stephen
signature.asc
Description: Digital signature
uld throw out encryption
just because we don't have a root cert available for use.
If we don't have a certificate it's not possible to validate *anyone*.
That's going to be the case for packagers and I just can't imagine
asking them to ship a broken configuration.
Thanks
t worth it. That causes
problems for our users when they're going to sites that are about a
billion times less likely to have been cracked into than Joe's crab shop
out on the internet. Encouraging people to believe that the PKI that's
currently being used for the web is actually meani
* Peter Eisentraut (pete...@gmx.net) wrote:
> On Friday 10 April 2009 21:32:29 Stephen Frost wrote:
> > A properly configured server could cause a failure too unless the client
> > is *also* properly configured. Sure, it's good for people to do. No, I
> > don't
ix is to have a warning/prompt (as pretty much all
web browsers today do) but then continue to connect. Also, the
web-browser analogy completely falls apart when you consider that the
use case is significantly different (how many times have you connected
to a PG server that you didn't know
definitely not apparent why such strictness should be the
> default behavior.
I agree with this. Avoiding spoofing is good, but so is on the wire
encryption even if you don't have anti-spoofing. This is a reasonable
set-up and we shouldn't just fail on it.
Stephen
signature.asc
Description: Digital signature
The following bug has been logged online:
Bug reference: 4503
Logged by: Stephen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Vista Home Premium
Description:failed to run initdb: 1!
Details:
I get the error: failed to run initdb: 1
o look for the other path!
Thanks,
Steve
---
Stephen Cuppett
SAS® Certified Advanced Programmer for SAS9®
Tel: +1 919 531 0659 ▪ [EMAIL PROTECTED]
www.sas.com
SAS® … THE POWER TO KNOW®
-Original Message
e already gone.
Steve
-------
Stephen Cuppett
SAS® Certified Advanced Programmer for SAS9®
Tel: +1 919 531 0659 ▪ [EMAIL PROTECTED]
www.sas.com
SAS® … THE POWER TO KNOW®
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 03, 2008 12:24 PM
To: Ste
I can upload the whole schema someplace, or is attaching a few files here okay?
Noticed that if I delete from the feature level, I do not hit the problem.
---
Stephen Cuppett
SAS® Certified Advanced Programmer
The following bug has been logged online:
Bug reference: 4396
Logged by: Stephen Cuppett
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: RHEL5.2 x86_64
Description:Trigger event fired "UPDATE" when "DELETE" happe
The following bug has been logged online:
Bug reference: 4001
Logged by: Stephen Clark
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: FreeBSD 6.2
Description:ecpg produces code that won't compile
Details:
Below is a code fragment
The following bug has been logged online:
Bug reference: 3784
Logged by: Stephen Bespalko
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Mac OS X 10.5
Description:pg_ctl fails to start server when called with -c
parameters
Details:
The
27;NULL AS' strings,
but till that's added it'd probably be best if psql error'd on this
like the backend does rather than accepting it and then not doing it.
Thanks!
Stephen
signature.asc
Description: Digital signature
ly when we say 'transaction', we're
meaning the a 'full' one and not a savepoint/release in the
documentation. The 'SET LOCAL' documentation even talks explicitly
about COMMIT and ROLLBACK being what causes a reset, RELEASE isn't
mentioned.
Thanks,
Stephen
signature.asc
Description: Digital signature
optionally, reset the role explicitly as well.
Of course, alternatively, we could have reset all apply to roles. I
don't honestly feel very strongly either way on that one.
Thanks,
Stephen
signature.asc
Description: Digital signature
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > At http://www.postgresql.org/docs/8.2/static/sql-set-role.html, we
> > claim that 'SESSION and LOCAL modifiers act the same as for the
> > regular SET command', bu
ly mention somehow under 'reset all' that 'reset role' isn't
done, and similairly that the documentation under 'set' doesn't apply
for 'set role'.
Thanks,
Stephen
signature.asc
Description: Digital signature
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > If you're saying we don't currently warn if a revoke leaves the
> > priviledges in-tact for the right and target, I'm not sure you can
> > currently get in a sta
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > Hmm. I'm not sure, but that may have been a case where it was generally
> > decided that the spec was somewhat braindead in this fashion (it seems
> > so in my personal view of
hich are being revoked, even if through someone else.
Perhaps that also implies that tracking the grantor is unnecessary.
Thanks,
Stephen
signature.asc
Description: Digital signature
omes when I do need it and it's not there. :)
Thanks,
Stephen
signature.asc
Description: Digital signature
The following bug has been logged online:
Bug reference: 2750
Logged by: Stephen haberman
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2 beta 3
Operating system: win32
Description:information_schema broken with primary and foreign key
on the same column
On 9/30/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"Stephen R. van den Berg" <[EMAIL PROTECTED]> writes:
> datalog=# vacuum verbose fnetsense;
> INFO: vacuuming "public.fnetsense"
> PANIC: right sibling is not next child in "fnetsense_utstamp_ke
The following bug has been logged online:
Bug reference: 2667
Logged by: Stephen R. van den Berg
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Linux 2.6.16.20 Debian (pg: 8.1.4-6)
Description:vacuuming a 70GB table causes a "
The following bug has been logged online:
Bug reference: 2461
Logged by: Stephen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows Server 2003
Description:pg_dump ftell mismatch error
Details:
HI,
I'm using pgadmin to back
The following bug has been logged online:
Bug reference: 2462
Logged by: Stephen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows Server 2003
Description:pg_dump ftell mismatch error (cont'd)
Details:
This is a continuati
The following bug has been logged online:
Bug reference: 2446
Logged by: Stephen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Windows Server 2003
Description:FATAL: Could not write to statistics collector pipe.
Details:
I'm ge
t in the process
for users to view).
Thanks,
Stephen
signature.asc
Description: Digital signature
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > Another approach would be to have PQsetdbLogin build up a conninfo
> > string and pass that into connectOptions1 instead of calling
> > connectOptions1 with an empty string a
* Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> On Tue, 14 Feb 2006, Stephen Frost wrote:
>
> > It's kind of a chicken-and-egg here because the backend decides what
> > authentication mechanism to ask for based off the username (at least in
> > part) through pg_hb
so be interesting to look into the Kerberos libraries to see why
they're attempting to malloc(0), perhaps there's a bug there when
Kerberos isn't set up on the machine?
Thanks,
Stephen
signature.asc
Description: Digital signature
strip"
dpkg-buildpackage -uc -us -rfakeroot
Should produce .debs in the parent directory which have debugging
information. Another useful build option is "noopt", ie:
export DEB_BUILD_OPTIONS="nostrip noopt", though that could make the
error go disappear. It'd be
perhaps on
the client you had something more recent?
Thanks,
Stephen
signature.asc
Description: Digital signature
matching your libpq and libkrb5
> RPMs you should be able to get better info.
We do have debugging .debs- for some things. We don't have them for
everything and unfortunately we don't yet have them for Postgres. I'll
talk to Martin about building some though so that in the future it's
easier to debug these problems.
Thanks,
Stephen
signature.asc
Description: Digital signature
command comes back as an error. If it's not too invasive
of a fix, I really think it should be included in the next point
release of 8.1.
Thanks!
Stephen
signature.asc
Description: Digital signature
also, which I hope Martin is
doing but honestly havn't gone back and checked on lately. :)
Thanks,
Stephen
signature.asc
Description: Digital signature
e you might consider looking at Oracle's
track record for fixing security issues. It's rather... poor. There
have been a number of articles to this affect on bugtraq recently, you
shouldn't have too much trouble finding good examples.
Enjoy,
Stephen
signature.asc
Description: Digital signature
s there much dependency on constraint names? If not, it'd seem like
implementing this would be pretty straight-forward. For some reason, I
thought there was some dependency on constraint names, but I can't
remember what...
Thanks,
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > test=> create table a (
> > test(> b int primary key
> > test(> );
> > NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "a_pkey" for=
>
would seem to me that \d can use its current format when the names are
the same, but if they're different it should display the index and the
constraint seperately.
Sorry, havn't really got time to write a patch at the moment. Hopefully
someone might have a minute to look into it tho.
Thanks,
Stephen
signature.asc
Description: Digital signature
uthentication token, the password isn't actually interesting in that
case).
Thanks,
Stephen
signature.asc
Description: Digital signature
The following bug has been logged online:
Bug reference: 1512
Logged by: Stephen Clouse
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Fedora Core 3
Description:Assertion failure (lock.c:1537) with SELECT FOR UPDATE
and savepoints
...
It would seem reasonable, then, that a grant of update privilege would
imply a grant of select privilege. Currently this isn't the case.
Stephen
signature.asc
Description: Digital signature
e pointers on the proper way to convert from unix
time to timestamp binary format either, btw. I was attempting to do
basically the same thing 'AbsoluteTimeUsecToTimestampTz', but
apparently that's not right. :)
Stephen
signature.asc
Description: Digital signature
t does not occur for them.
I am using postgresql 7.4.1 on Debian sid/unstable (i386).
Thanks in advance,
Stephen Quinney
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Reece Hart <[EMAIL PROTECTED]> writes:
> > I have a hunch about why this happens and is rare. The pftype_id_lookup
> > function was created AFTER some of the tables using 'alter table set
> > default ...'. Thus, the function's OID is greater than the OID of t
#x27; again, at least for that database
and possibly overall. Havn't had a chance to play with it yet but it
seems pretty straight-forward to repeat.
Stephen
pgp0.pgp
Description: PGP signature
deferred);
insert into a values (7);
begin;
insert into b values (-7);
update b set ia=-ia where ia<0;
commit;
drop table a;
drop table b;
--
Sincerely, [EMAIL PROTECTED]
Stephen R. van den Berg (AKA BuGless).
"-- hit
On Sat, 4 May 2002, Tom Lane wrote:
> Stephen Amadei <[EMAIL PROTECTED]> writes:
> > However, if someone was to know that Postgres needs a /bin/rm, an exploit
> > could be created that runs /bin/rm instead of /bin/sh and trashes the
> > databases postgres owns.
n /usr/local/pgsql/data and then
'cp -aRp'ing it into the chroot. So I had two copies of the same corrupt
database.
Thanks for the help.
Steve
Stephen Amadei
Dandy.NET! CTO
Atlantic City, NJ
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
bring this idea up mostly because I think others may wish to put
Postgres in a chrooted environment, and this small coding change will
help them. I also wondered if any odd side effects would occur...
Steve
Stephen Amadei
Dandy.NET! CTO
Atlantic City, NJ
On Fri, 3 May 2002, Tom Lane wrote:
> Stephen Amadei <[EMAIL PROTECTED]> writes:
> >> Urgh. Can you provide a stack trace?
>
> > You mean using strace? Yeah. The strace created quite a bit of logs, but
> > the process that segfaulted is included below.
>
&g
On Fri, 3 May 2002, Tom Lane wrote:
> Stephen Amadei <[EMAIL PROTECTED]> writes:
> > I have been trying to run Postgres 7.2.1 in a chrooted environment, but
> > once I try to connect to the server with a "psql -l", it segfaults as it
> > tries to read from
and rm programs directly (and placed /bin/cp and /bin/rm in the chroot
jail) as a quick fix... I feel it gives a bit more security.
Can anyone tell me if there is any inherently bad side effects to this?
Or why the "system" call is necessary?
S
1 - 100 of 105 matches
Mail list logo
