I'm noticing a couple of unexpected warnings on an x86_64 machine:
descriptor.c: In function 'ECPGset_desc':
descriptor.c:506: warning: passing argument 1 of 'ECPGget_variable' from
incompatible pointer type
This probably needs the same hack as in execute.c.
pgc.l:1094: warning, -s option given
On Thu, Oct 13, 2005 at 04:24:23PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Thu, Oct 13, 2005 at 01:30:56PM -0400, Tom Lane wrote:
> >> Basically, DECLARE introduces a new name scope that wouldn't be there
> >> if you didn't say DECLARE. Without some bizarre reint
[ redirecting to a more appropriate list ]
[EMAIL PROTECTED] writes:
> I've noticed that, even though I specified LOCAL5 as syslog facility,
> postgres
> nevertheless logs _some_ events to LOCAL0.
I've thought of a theory about this: if the first write_syslog() call
occurs before guc.c has rea
"Martin Pitt" <[EMAIL PROTECTED]> writes:
> Currently the postmaster requires the private SSL key file to have the same
> owner as the postmaster, and no permissions for group and others. However,
> this is too strict to sensibly use the certificate with ACLs, which permits
> other server processes
Tom Lane wrote:
> Dennis Vshivkov <[EMAIL PROTECTED]> writes:
> > The problem is that the code that updates pg_group file resolves
> > group membership through the system user catalogue cache.
>
> Good catch.
>
> > The attached `98-6-pg_group-stale-data-fix.patch' makes the code
> > in question a
Dennis Vshivkov <[EMAIL PROTECTED]> writes:
> The problem is that the code that updates pg_group file resolves
> group membership through the system user catalogue cache.
Good catch.
> The attached `98-6-pg_group-stale-data-fix.patch' makes the code
> in question access the system user table dire
"Kevin Walker" <[EMAIL PROTECTED]> writes:
>ERROR: role "dbadmin" is a member of role "kw"
> The message suggests that the login role "kw" is already a member of group
> role "dbadmin" which is not the case.
I think you are reading it backwards. You're probably accidentally
trying to set up
On Thu, Oct 13, 2005 at 03:51:15PM +, Karl O. Pinc wrote:
> I definately do not recall catching any additional errors at
> compile time as part of the switch to 8.
8.0's syntax checking is minimal; 8.1's will be better. Also, you
might not even have plpgsql's lanvalidator function if you rest
The following bug has been logged online:
Bug reference: 1963
Logged by: Martin Pitt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1beta3
Operating system: Debian
Description:SSL certificate permission check is too strict
Details:
Currently the postmaster r
Kevin Walker wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1964
> Logged by: Kevin Walker
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1 beta 3
> Operating system: Windows XP
> Description:Role membership error
> Details:
>
>
On Thu, Oct 13, 2005 at 11:18:13AM -0500, C Wegrzyn wrote:
> Yes I found out the same thing. Unfortunately it isn't quite that
> simple for me. It isn't a very good idea to hard-code fixed sizes in
> executables. I have a file with all sorts of #defines in it. If the bug
> doesn't get fixed it mea
On Thu, Oct 13, 2005 at 09:53:14PM -0400, Bruce Momjian wrote:
> Good catch! I have backpatched these fixes to the 8.0 and 7.4 branches
> as you suggested, (identical) patches attached.
Thanks Bruce. This was an oversight on my part. I should have committed
to 8.0 branch too. I'm sorry about that
Tony Caduto wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1966
> Logged by: Tony Caduto
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: Linux
> Description:Single OUT PARM does not return param name.
> Details
The following bug has been logged online:
Bug reference: 1966
Logged by: Tony Caduto
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Linux
Description:Single OUT PARM does not return param name.
Details:
When creating a plpgsql function th
The following bug has been logged online:
Bug reference: 1965
Logged by: Wilmar Yesid Calderón Franco
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP
Description:documentation
Details:
information about new versions.
-
Package: postgresql-8.0
Version: 8.0.3-13
Severity: important
Tags: patch, upstream
Here's the problem:
db=# CREATE GROUP g1;
CREATE GROUP
db=# CREATE USER u1 IN GROUP g1;(1)
CREATE USER
# cat /var/lib/postgresql/8.0/main/global/pg_group
#
The file gets rewritten, but th
On 10/13/2005 09:38:36 AM, Bruce Momjian wrote:
> Fair enough. At the same time it sure would be nice if
> plpgsql actually compiled (and parsed SQL) at
> function definition time, even when the result is thrown away.
> I'm building a big system and it's quite annoying
> to get syntax errors,
Michael Fuhr wrote:
>On Thu, Oct 13, 2005 at 02:24:27PM +0100, Charles Wegrzyn wrote:
>
>
>>I have code that under 8.0.3 works:
>>
>> VARCHAR t[MAX_TENANT_SIZE+1];
>> VARCHAR o[MAX_OID_SIZE+1];
>>
>>In 8.0.4 I found this throws an error during the ecpg step:
>>
>>tenant.ec:375: ERROR: pointer
On Oct 13, 2005, at 9:54 AM, Tom Lane wrote:
Are you sure this bug report shouldn't be directed to Apple?
Of course it should. I only directed it to you because I had thought
you figured out a workaround for it. If there isn't a workaround, I
won't report it again. :-)
Thanks,
David
-
Hi Tom,
Thanks, that got me passed that step, but make failed on another. My production site is stuck with 7.3.10 (RHEL 3.0), and I would like to have a separate development site on a OS X 10.4 machine, but alas, it seems I'll have to keep them together.
On 10/13/2005 03:24:23 PM, Tom Lane wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Thu, Oct 13, 2005 at 01:30:56PM -0400, Tom Lane wrote:
>> Basically, DECLARE introduces a new name scope that wouldn't be
there
>> if you didn't say DECLARE. Without some bizarre reinterpretation
of the
>
The following bug has been logged online:
Bug reference: 1967
Logged by: tadayoshi sato
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.4
Operating system: WindowsXp ,Linux (redhat9)
Description:Respons(Binary) is not correctly by PQexecParams
Details:
Wh
The following bug has been logged online:
Bug reference: 1964
Logged by: Kevin Walker
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1 beta 3
Operating system: Windows XP
Description:Role membership error
Details:
I created a group role called dbadmin and as
23 matches
Mail list logo
