Giles Lean <[EMAIL PROTECTED]> writes:
>>> utimes("/tmp/.s.PGSQL.5432", (const struct timeval *) 0);
>>
>> Hm, do you think that's portable?
> Hm ... yes, actually I do. I use it on HP-UX, and testing indicates
> that it works on FreeBSD, Linux, NetBSD and Tru64 as well.
> Thinking about it, a
Tom Lane <[EMAIL PROTECTED]> writes:
> Giles Lean <[EMAIL PROTECTED]> writes:
>
> > utimes("/tmp/.s.PGSQL.5432", (const struct timeval *) 0);
>
> Hm, do you think that's portable?
Hm ... yes, actually I do. I use it on HP-UX, and testing indicates
that it works on FreeBSD, Linux, NetBSD and
Andrew Fyfe ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
jdbc "update row" can mess up other columns
Long Description
The attached program when run gives me the following output
DatabaseProductName: PostgreSQL
DatabaseProduc
[EMAIL PROTECTED] writes:
> When calling a function declared SECURITY DEFINER, I get permission
> denied errors on schemas that the function would access.
This is hard to believe. Please give a complete example.
regards, tom lane
---(end of broadc
[EMAIL PROTECTED] writes:
> Query failed: ERROR: Bad timestamp external representation '06/05/2002 11:42:10 ART'
> PostgreSQL 7.2.3 on i586-pc-linux-gnu, compiled by GCC 2.96 (redhat 7.2, postgres
>installed from sources)
Timezone 'ART' is in the list of timezones known to Postgres, but the
tab
Folks,
Bug reported off IRC:
MONEY Type cannot be cast to any other type, preventing migration from this
depreciated data type.
Affects: 7.2.3, 7.3.1
Frequency: 100% Reproducable
Effect When Occurring: Unable to convert, query data
Difficulty of Fix: Easy, probably
Certianty of Diagnosis:
Jason B. Alonso ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Schema access not inherited by functions declared SECURITY DEFINER
Long Description
When calling a function declared SECURITY DEFINER, I get permission denied error
"Kinsey, Ben" <[EMAIL PROTECTED]> writes:
> Here's a little more detail as to how this socket file was getting deleted:
> On the system I'm using, if you attempt to start postmaster when an instance
> of it is already running, the socket file gets deleted. It was discovered
> that upon bootup of t
Giles Lean <[EMAIL PROTECTED]> writes:
> Either teach your /tmp cleaner not to clean out the socket files as
> Tom Lane suggested, or arrange to update the socket timestamps. I
> think it's easier to just keep updating the timestamps -- then I don't
> have to educate each new system administrator.
[ Where *did* that Reply-To: line come from -- it's broken ...
repl: bad addresses:
[EMAIL PROTECTED]; -- extraneous semi-colon
]
> Stopping and starting the postmaster daemon clears up this problem,
> but this problem creeps up about 2 times a week, and is a major
> annoyance.
Either
On Fri, 2003-01-24 at 06:16, Bhuvan A wrote:
> > Long Description PostgreSQL has mechanism for commenting databases.
> > Database comments can by read by obj_description(oid), psql \l+ command
> > use it. Database comments should be global, but they are not, when we do
> > \l+ on one database, and
> Long Description PostgreSQL has mechanism for commenting databases.
> Database comments can by read by obj_description(oid), psql \l+ command
> use it. Database comments should be global, but they are not, when we do
> \l+ on one database, and then on other, results will be different. I
> conside
12 matches
Mail list logo
