On 12/17/2005 10:21:39 PM, Michael Glaesemann wrote:
On Dec 18, 2005, at 13:25 , Karl O. Pinc wrote:
On a related note is there some reason why
interval + int
does not result in the interval plus int number
of seconds?
Why should the int necessarily represent seconds and not some other
amo
"Karl O. Pinc" <[EMAIL PROTECTED]> writes:
> What is the best way to convert an integer number of
> seconds past midnight into a time?
Intermediate 'interval' value seems to work:
regression=# select (99.44 * '1 second'::interval)::time;
time
-
00:01:39.44
(1 row)
> On a re
On Dec 18, 2005, at 13:25 , Karl O. Pinc wrote:
What is the best way to convert an integer number of
seconds past midnight into a time?
Try your_date::timestamptz + your_seconds * interval '1 sec', e.g.,
test=# select current_date::timestamptz, current_date::timestamptz +
1000 * interval '
On 12/17/2005 08:33:02 AM, Russ Brown wrote:
Is the documentation not available online somewhere?
There is always the CVS web interface:
http://developer.postgresql.org/cvsweb.cgi/pgsql/
Karl <[EMAIL PROTECTED]>
Free Software: "You don't pay back, you pay forward."
-- Rober
Hi,
What is the best way to convert an integer number of
seconds past midnight into a time? I can't seem to
figure out a way that does not involve casts to strings,
which seems wasteful.
On a related note is there some reason why
interval + int
does not result in the interval plus int number
of
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Greg Stark wrote:
> > Using iso-8859-1 to encode "é" as a single byte versus using UTF8
> > which would take two bytes to encode it is an issue of using two
> > *different* encodings.
>
> But that's not what we are discussing.
The poster to which To
Greg Stark wrote:
> Using iso-8859-1 to encode "é" as a single byte versus using UTF8
> which would take two bytes to encode it is an issue of using two
> *different* encodings.
But that's not what we are discussing.
> There is a separate issue that some characters could theoretically
> have mult
Tom Lane <[EMAIL PROTECTED]> writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > By the way, I have always been concerned about the feature of Unicode
> > that you can write logically equivalent strings using different
> > code-point sequences. Namely, you often have the option of writi
On Sat, Dec 17, 2005 at 03:39:02PM -0800, Bob Pawley wrote:
> The following gives me the information, but the rows are duplicated
> from one to three times. I would like to see one row for each of the
> values. I have attempted a number of variations but they all give me
> similar duplication.
>
>
I have a table, Devices, with various values under the column
Type.
I wish to view all of the information regarding two of these values
'monitor' and 'valve'.
The following gives me the information, but the rows are
duplicated from one to three times. I would like to see one row
for eac
Martijn van Oosterhout writes:
> I think the real solution is to implement COLLATE support.
Maybe so, but we still need to figure out what we're doing for the back
branches, and that won't be it ...
regards, tom lane
---(end of broadcast)-
On 12/17/05, Harry Jackson <[EMAIL PROTECTED]> wrote:
On 12/17/05, hubert depesz lubaczewski <[EMAIL PROTECTED]> wrote:> must have missed that one. thanks - we are moving to 8.1 anyway (50-150%> increase in performance for some specific tasks!).
For which tasks in particular are you seeing this ki
On Sat, Dec 17, 2005 at 02:08:06PM -0500, Tom Lane wrote:
> The weight of opinion later in the thread seems to be leaning towards
> the idea that we do not want to accept the word of strcoll/strxfrm about
> whether two strings are equal: there are too many scenarios where lax
> equality behavior wo
Tom Lane wrote:
> Joe Conway <[EMAIL PROTECTED]> writes:
> > I'm happy to lump all the docs back into the README if that's what you
> > want, but I split it up in the first place because it was getting very long.
>
> No, I'm not really proposing that we force all contrib modules to have
> only a
Joe Conway <[EMAIL PROTECTED]> writes:
> I'm happy to lump all the docs back into the README if that's what you
> want, but I split it up in the first place because it was getting very long.
No, I'm not really proposing that we force all contrib modules to have
only a README. I'm just annoyed by
Tom Lane wrote:
Actually, I don't think you can reasonably blame the Debian packager
for having overlooked the fact that contrib/dblink has more
documentation files besides its README. The PGDG RPM people overlooked
that too, as did Red Hat (ie, me).
Well, in my own defense, I pointed out the
Regarding, http://archives.postgresql.org/pgsql-general/2003-10/msg00956.php
Has there been any progress integrating aspell for tsearch2 over ispell?
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Tom Lane wrote:
Bruce Momjian writes:
Where are we on this?
Waiting to see if there's any input on what the behavior needs to be.
Actually, "potyty" and "potty" are not equal in Hungarian language. We
use the "tyty" form in complex words. Only data sorting requires the
knowledg
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> By the way, I have always been concerned about the feature of Unicode
> that you can write logically equivalent strings using different
> code-point sequences. Namely, you often have the option of writing an
> accented letter using the "legacy" sin
Jerry Sievers wrote:
> Afraid though of having anything go flakey when we import the
> original DBs with LATIN1 encoding.
LATIN1 and LATIN9 are almost the same, so unless you have Euro
characters or some other corner cases in your data, you should just go
ahead with this. Note that changing to
Tom Lane wrote:
> Perhaps the fast-path check is a bad idea, but fixing this is not
> just a matter of removing that. If we subscribe to strcoll's
> worldview then we have to conclude that *text strings are not
> hashable*, because strings that should be "equal" may have different
> hash codes.
B
Tino Wildenhain <[EMAIL PROTECTED]> writes:
> Am Samstag, den 17.12.2005, 16:53 +0200 schrieb Andre Truter:
>> I would be nice if the documentation could be online though, then I
>> would not need to download the whole postgres source just to get the
>> documentation for one small part.
> This is
Yes, I think the only official PGDG stuff is source. The binaries are
done by port-specific teams. PGDG doesn't deal with MSI installer
issues, or RPM issues, only the port-specific teams do. I know I don't
read any RPM emails and any MSI issues are dealt with by the Win32
people.
Bruce us
Joshua D. Drake wrote:
>
> >The distinction is that RPMs and pginstaller are port-specific, binary
> >distributions.
> >
> >
> So they can't be considered official port releases for the PGDG? They
> are not "forks".
> Or, are you saying that the only official PGDG release is the source?
Yes, I
On Sat, 2005-12-17 at 17:09 +0100, Tino Wildenhain wrote:
>
> This is understandable ;) But in this case not postgres peoples
> fault.
Yes, I realise it is not the fault of the postgres people and I did not
intend to make it sound like that.
I am a bit disappointed that the rpm package that co
The distinction is that RPMs and pginstaller are port-specific, binary
distributions.
So they can't be considered official port releases for the PGDG? They
are not "forks".
Or, are you saying that the only official PGDG release is the source?
Sincerely,
Joshua D. Drake
--
The PostgreSQ
Joshua D. Drake wrote:
>
> >>Well they are kept on PostgreSQL.Org servers, they are called PGDG
> >>rpms... I don't
> >>think you can get much more official then that.
> >>
> >>
> >
> >I think they are official like pginstaller/Win32 is official. It is
> >endorsed by our project, but sort of
Bruce Momjian writes:
> Where are we on this?
Waiting to see if there's any input on what the behavior needs to be.
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desir
Well they are kept on PostgreSQL.Org servers, they are called PGDG
rpms... I don't
think you can get much more official then that.
I think they are official like pginstaller/Win32 is official. It is
endorsed by our project, but sort of separate too.
O.k. well now I am confused... Wh
Joshua D. Drake wrote:
>
> >>>
> >>>
> >>Actually, I think this should be incoporated into a spec file
> >>specifically for suse within the PGDG rpms.
> >>
> >>
> >
> >The PostgreSQL Global Development Group has official RPMs? I didn't
> >know. When Lamar did it it was always unoffici
Actually, I think this should be incoporated into a spec file
specifically for suse within the PGDG rpms.
The PostgreSQL Global Development Group has official RPMs? I didn't
know. When Lamar did it it was always unofficial.
Well they are kept on PostgreSQL.Org servers, they ar
Joshua D. Drake wrote:
> Bruce Momjian wrote:
>
> >This patch should be sent to SuSE, not PostgreSQL.
> >
> >
>
> Actually, I think this should be incoporated into a spec file
> specifically for suse within the PGDG rpms.
The PostgreSQL Global Development Group has official RPMs? I didn't
kn
Where are we on this? Given the original report:
online=# select * from common_logins where username = 'potyty';
uid | username | password | lastlogin | status | usertype | loginnum
-+--+--+---++--+--
(0 rows)
Bruce Momjian wrote:
This patch should be sent to SuSE, not PostgreSQL.
Actually, I think this should be incoporated into a spec file
specifically for suse within the PGDG rpms.
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replic
On 12/17/05, hubert depesz lubaczewski <[EMAIL PROTECTED]> wrote:
> must have missed that one. thanks - we are moving to 8.1 anyway (50-150%
> increase in performance for some specific tasks!).
For which tasks in particular are you seeing this king of gain?
Harry
--
http://www.hjackson.org
http
Am Samstag, den 17.12.2005, 16:53 +0200 schrieb Andre Truter:
...
> Thanks, I'll download the Posgres source then.
>
> I would be nice if the documentation could be online though, then I
> would not need to download the whole postgres source just to get the
> documentation for one small part.
Thi
We have a TODO also:
o Allow TIMESTAMP WITH TIME ZONE to store the original timezone
information, either zone name or offset from UTC [timezone]
If the TIMESTAMP value is stored with a time zone name, interval
computations should adjust based on the time zon
On Sat, 2005-12-17 at 14:53 +, Greg Sabino Mullane wrote:
> > Is the documentation not available online somewhere?
>
> Quick version for you:
>
> http://www.gtsm.com/dblink/
>
>
Great!
This is exactly what I want.
Thanks Greg!
--
Andre Truter | Software Engineer | Registered Linux user
This patch should be sent to SuSE, not PostgreSQL.
---
Weberhofer GmbH wrote:
> Dear Steve,
>
> I have had the same problem related SuSE 8.2. A thing that additionally can
> be wrong is the LC_CTYPE setting in the environm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is the documentation not available online somewhere?
Quick version for you:
http://www.gtsm.com/dblink/
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200512170951
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9067149
On Sat, 2005-12-17 at 09:21 -0500, Douglas McNaught wrote:
> Andre Truter <[EMAIL PROTECTED]> writes:
>
> > On Sat, 2005-12-17 at 07:04 -0700, Leonel Nunez wrote:
> >
> >> download the source for your PostgreSQL version unpackit
> >> and check onthe contrib/dblink dir
> >>
> >
> > Yes
"Russ Brown" <[EMAIL PROTECTED]> writes:
> Is the documentation not available online somewhere?
For the stuff in 'contrib', I don't think so. Might be a good project
for someone. :)
-Doug
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postm
On Sat, 17 Dec 2005 08:21:29 -0600, Douglas McNaught <[EMAIL PROTECTED]>
wrote:
Andre Truter <[EMAIL PROTECTED]> writes:
On Sat, 2005-12-17 at 07:04 -0700, Leonel Nunez wrote:
download the source for your PostgreSQL version unpackit
and check onthe contrib/dblink dir
Yes, th
Andre Truter <[EMAIL PROTECTED]> writes:
> On Sat, 2005-12-17 at 07:04 -0700, Leonel Nunez wrote:
>
>> download the source for your PostgreSQL version unpackit
>> and check onthe contrib/dblink dir
>>
>
> Yes, that is what I have been trying to do, but where do I download the
> dblink
On Sat, 2005-12-17 at 07:04 -0700, Leonel Nunez wrote:
> download the source for your PostgreSQL version unpackit
> and check onthe contrib/dblink dir
>
Yes, that is what I have been trying to do, but where do I download the
dblink source from?
--
Andre Truter | Software Engineer
Andre Truter wrote:
On Sat, 2005-12-17 at 06:20 -0700, Leonel Nunez wrote:
It's on the contrib package
No, unfortunately the SUSE people did not include it in the contrib
package.
or in the contrib dir if you installed from source
Installed from rpm package.
I have se
At 11:49 AM 12/17/2005 +0800, Lincoln Yeoh wrote:
But in a column for license owner names, one might want "tty" and "tyty"
to be the same - one might have to have a multicolumn index depending on
the owner's locale of choice.
To make myself clear, one might want to store a person's name in one
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] 8.1 build on Solaris has LATIN9?
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
From: Jerry Sievers <[EMAIL PROTECTED]>
Date: 16 Dec 2005 16:42:37 -0500
In-Reply-To: Tom Lane's message of "Fri, 16 Dec 2005 15:28:43 -0500"
Message-ID: <[EM
On Sat, 2005-12-17 at 06:20 -0700, Leonel Nunez wrote:
>
> It's on the contrib package
No, unfortunately the SUSE people did not include it in the contrib
package.
> or in the contrib dir if you installed from source
>
Installed from rpm package.
I have searched for the dblink source to ge
Andre Truter wrote:
Where do I find documentation for using dblink?
I am running PostgreSQL 8.03 on SuSE 9.3 and I installed the
postgresql-contrib package, but it only includes the README for dblink,
which only lists the functions, but it does not include any information
on how to use it.
For
Where do I find documentation for using dblink?
I am running PostgreSQL 8.03 on SuSE 9.3 and I installed the
postgresql-contrib package, but it only includes the README for dblink,
which only lists the functions, but it does not include any information
on how to use it.
For instance, it would lis
On 12/16/05, Tom Lane <[EMAIL PROTECTED]> wrote:
2005-08-09 17:14 tgl * src/backend/postmaster/pgstat.c: Make backends that are readingthe pgstats file verify each backend PID against the PGPROC array.Anything in the file that isn't in PGPROC gets rejected as being a
> At 01:40 PM 12/16/2005 -0500, Tom Lane wrote:
> >Nobody's said anything about giving up locale-sensitive sorting. The
> >question is about locale-sensitive equality: does it really make sense
> >that 'tty' = 'tyty'? Would your answer change in the context
> >'/dev/tty' = '/dev/tyty'? Are you w
53 matches
Mail list logo
