Wade Klaver <[EMAIL PROTECTED]> writes:
> I guess what I am trying
> to say is that the date_part() call is how you determine what you are
> asking... If I want to get the number of years, it shouldn't matter if my
> interval is '1 year, 1 month' or '396 days', they both contain 1 year.
I thin
siva wrote:
> how to solve this problum
>
> Warning: pg_exec(): Query failed: could not receive data from server: Broken pipe
I would look in the server logs to see if the backend died unexpectedly.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
Fixed and backpatched to 7.4.X. Thanks, though those lines are
commented out with --, so I am not sure why it is causing you a problem.
---
PostgreSQL Bugs List wrote:
>
> The following bug has been logged online:
>
> Bug
Hello again,
Should an interval not be arbitrary? The portion of the information one
requests should not depend on the representation. I guess what I am trying
to say is that the date_part() call is how you determine what you are
asking... If I want to get the number of years, it shouldn't
Look at this:
test=> CREATE SEQUENCE x;
CREATE SEQUENCE
test=> \d x
Sequence "public.x"
Column | Type
---+-
sequence_name | name
last_value| bigint
increment_by | bigint
Hello,
I have a problem with my program that inserts records into postgreSQL
database.
After continuously running for several days, it suddenly hangs. Attaching
with
gdb to a process gives the following stack trace. It seems like a few
people
reported this problem but I haven't seen anyone sug
how to solve this problum
Warning: pg_exec(): Query failed: could not receive
data from server: Broken pipe
The following bug has been logged online:
Bug reference: 1081
Logged by: Aarjav Trivedi
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux
Description:Spelling error in tsearch2.sql leading to problems with
tsearch
Details:
On li
Right. Sorry. My brain was over on parameter issues and
I did not reread my original bug...
On Fri, Feb 20, 2004 at 01:03:08PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Shouldn't all function calls go (through fast path or fmgr
> > or the language manager?) to a centralized p
elein <[EMAIL PROTECTED]> writes:
> Shouldn't all function calls go (through fast path or fmgr
> or the language manager?) to a centralized parameter marshalling?
We're talking about what happens inside the function, not how you pass
parameters to it.
regards, tom lane
Robert Treat <[EMAIL PROTECTED]> writes:
> so ISTM that your example is certainly a deficiency if not a bug.
I believe it is a bug or at least an unimplemented feature in plpgsql:
plpgsql has its own implementation of casting, and is not aware that
casting to a domain should involve running check
On Thu, Feb 19, 2004 at 16:52:37 -0800,
Wade Klaver <[EMAIL PROTECTED]> wrote:
> Hello folks.
>
> I just noticed some funky behaviour on the part of date_part. If there is
> some reason this is correct behaviour, I wouldn't mind knowing why.
> The problem is that date_part can return different
Hi Tom,
--- Tom Lane <[EMAIL PROTECTED]> a écrit : >
=?iso-8859-1?q?Laurent=20FAILLIE?=
> <[EMAIL PROTECTED]> writes:
> > Is it possible to improve "configure" script of
> > postgresql to allow to specify in which directory
> a
> > 3rd tool is installed ?
>
> See --with-includes and --with-libra
13 matches
Mail list logo
