Robert Haas writes:
> On Wed, Aug 17, 2011 at 1:21 AM, raf wrote:
>> so, there is either a plpgsql parser bug that treats the sql equality
>> operator as the plpgsql assignment operator, or "=" is an undocumented
>> alternative to the documented plpgsql assignment operator (":=").
> I think it's
On mån, 2011-04-25 at 11:03 -0400, Robert Haas wrote:
> >> but executing
> >>time make -j4 check
> >> fails (I don't see any obvious problem in the log file):
> >> [...]
> >> == creating temporary installation
> ==
> >>
> >> pg_regress: installation failed
> >> Examine
On Wed, Aug 17, 2011 at 1:21 AM, raf wrote:
> so, there is either a plpgsql parser bug that treats the sql equality
> operator as the plpgsql assignment operator, or "=" is an undocumented
> alternative to the documented plpgsql assignment operator (":=").
I think it's the latter. I have a vague
Tom Lane writes:
> The case where this would actually happen is where extension A creates
> some operator, and mentions some other operator as its commutator or
> negator, but never gets around to defining the other operator. Then
> extension B comes along and tries to fill in the other operator
Dimitri Fontaine writes:
> ... My fix is
> to have deleteDependencyRecordsFor use true for skipExtensionDeps.
On further reflection, there's some merit in that fix too. The question
is what do we think should happen if the pre-existing shell operator
belongs to another extension. It seems like
The following bug has been logged online:
Bug reference: 6173
Logged by:
Email address: pete_w...@symantec.com
PostgreSQL version: 8.3.14
Operating system: Windows Server 2003 x64 Enterprise Edition
Description:8.3.14 and 8.3.15 do not work on Win2k3x64
Details:
He
"Robert Hopek" wrote:
> Why do you have the configuration option to change the pgsql
> socket (which we need to do for our jailed shell environment), but
> not have psql check the postgresql.conf file for the enablement of
> that location change so that psql would look there automatically?
We
Dimitri Fontaine writes:
> But in makeOperatorDependencies() we find the following piece of code:
> /* In case we are updating a shell, delete any existing entries */
> deleteDependencyRecordsFor(myself.classId, myself.objectId, false);
> false is for bool skipExtensionDeps.
> And n
"Robert Hopek" writes:
> Why do you have the configuration option to change the pgsql socket (which
> we need to do for our jailed shell environment), but not have psql check the
> postgresql.conf file for the enablement of that location change so that psql
> would look there automatically?
How w
Tom Lane writes:
> I'm betting it's got something to do with
> http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=eb15f26d577a11319b9429fb84f752a0135918db
You're right, once more. Here's what I understand is happening from
reading the code. No patch attached, the scope of change
"Robert Hopek" writes:
> coding), existing software, such as phpPgAdmin, are stuck only looking in
> /tmp for it.
Did you try host=/custom/path/to/the/socket/?
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-bugs mailing li
On 08/20/11 8:31 AM, Robert Hopek wrote:
The following bug has been logged online:
Bug reference: 6171
Logged by: Robert Hopek
Email address: rho...@getnetworks.com
PostgreSQL version: 8.1.23
Operating system: CentOS/RHEL
Description:Sockets Issue
Details:
Why do yo
You must to do some modifications on User Accounts on your mac:
1. Open User preferences after from Postgres Instalation
2. Rename user PostgresSQL to postgres
3. Enable the administrator permisions.
4. Execute newly the Postgres instaler.
regards,
Alejandro Sánchez
Postgres DBA
--
View this m
The following bug has been logged online:
Bug reference: 6171
Logged by: Robert Hopek
Email address: rho...@getnetworks.com
PostgreSQL version: 8.1.23
Operating system: CentOS/RHEL
Description:Sockets Issue
Details:
Why do you have the configuration option to change
14 matches
Mail list logo
