Hello all,
I've got an issue with the ODBC component with PostgreSQL (v 7.3.4-2 in
Cygwin). I've connected to my DB using MS Access, and things seemed to be
working reasonably well.
However, when I exported a table to the DB from Access, while it shows up in
the list of tables in the DB, if I
Phil Campaigne <[EMAIL PROTECTED]> writes:
> -bash-2.05b$ ldd /usr/local/pgsql/lib/libpq.so.3
> libcrypt.so.1 => /lib/libcrypt.so.1 (0x4001d000)
> libresolv.so.2 => /lib/libresolv.so.2 (0x4004a000)
> libnsl.so.1 => /lib/libnsl.so.1 (0x4005a000)
> libc.so.6 => /li
Hello,
Is it possible to make PL/PGSQL stored procedures with a variable number
of args ?
If yes, is it possible to have a sample ?
Thanks you in advance :-)
---
Bruno BAGUETTE - [EMAIL PROTECTED]
---(end of broadcast)--
Arguile <[EMAIL PROTECTED]> writes:
> On Tue, 2003-09-30 at 07:06, Mike Mascari wrote:
> [snip]
> > CREATE INDEX i_employees ON employees(lower(name));
> >
> > Let's also assume that the lower() function is computationally
> > expensive. Now if I have a query like:
> >
> > SELECT lower(name)
> >
Hi Tom,
THanks for your response. Here are my results:
-bash-2.05b$ ldd /usr/local/pgsql/bin/psql
libpq.so.3 => /usr/local/pgsql/lib/libpq.so.3 (0x40013000)
libz.so.1 => /usr/lib/libz.so.1 (0x4002f000)
libreadline.so.4 => /usr/lib/libreadline.so.4 (0x4003d000)
libte
We run MySQL as the backend ;)
Bill Bell wrote:
When I request
http://www.postgresql.org
all I get is a light grey line on a dark grey background and the HTML
is correspondingly "uninformative".
Tried looking a couple of days ago, thought it must just be some
transient problem.
Anybody know?
B
tgl wrote:
> strk <[EMAIL PROTECTED]> writes:
> > If I run that again, *exactly the same query*:
> > PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
> > 566 pgsql 14 0 126M 126M 3396 S 0.0 16.8 7:13 postmaster
>
> > It looks like someone is leaking memory, eit
Quoting Bruno BAGUETTE <[EMAIL PROTECTED]>:
> > I'm personally using mod_auth_pgsql against a user table with
> > encrypted passwords. To properly encrypt them I am using the
> > contrib pgcrypto module and something like
>
> Hello,
>
> Can you tell me what version of mod_auth_pgsql do you us
On Tue, 2003-09-30 at 09:54, Mike Mascari wrote:
> Arguile wrote:
>
> > On Tue, 2003-09-30 at 07:06, Mike Mascari wrote:
> >
> >>CREATE INDEX i_employees ON employees(lower(name));
> >>
> >>Let's also assume that the lower() function is computationally
> >>expensive. Now if I have a query like:
>
On Tue, 30 Sep 2003, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > In 7.3 and less ssl connections fail if a host line matches before the hostssl
> > line. At least I think that's the situation, there is definitely something
> > there that will make a ssl connection get reje
Arguile wrote:
> On Tue, 2003-09-30 at 07:06, Mike Mascari wrote:
>
>>CREATE INDEX i_employees ON employees(lower(name));
>>
>>Let's also assume that the lower() function is computationally
>>expensive. Now if I have a query like:
>>
>>SELECT lower(name)
>>FROM employees
>>WHERE lower(name) = 'mik
strk <[EMAIL PROTECTED]> writes:
> dblasby wrote:
>> Hum - this shouldnt do anything.
>> The aggregate should have "null" as its initial value.
>> GeomUnion(null,) --> null.
>> So, you'll end up with null *very* quickly because
>> GeomUnion(null,) returns null without any actual execution.
> It l
When grilled further on (Tue, 30 Sep 2003 09:26:19 -0400),
Mike Leahy <[EMAIL PROTECTED]> confessed:
> I have a query that calculates various using variables from a survey
> database. As with any survey, there are many instantces of null values. I'm
> wondering if there is any way to escape th
Arguile <[EMAIL PROTECTED]> writes:
> On Tue, 2003-09-30 at 07:06, Mike Mascari wrote:
>> SELECT lower(name)
>> FROM employees
>> WHERE lower(name) = 'mike'
>>
>> will PostgreSQL re-evaluate lower(name)? Is it necessary?
> No, it won't re-evaluate.
I think he's asking whether the lower(name) app
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> In 7.3 and less ssl connections fail if a host line matches before the hostssl
> line. At least I think that's the situation, there is definitely something
> there that will make a ssl connection get rejected even if there is an
> appropiate entry in
On Tue, 2003-09-30 at 07:06, Mike Mascari wrote:
[snip]
> CREATE INDEX i_employees ON employees(lower(name));
>
> Let's also assume that the lower() function is computationally
> expensive. Now if I have a query like:
>
> SELECT lower(name)
> FROM employees
> WHERE lower(name) = 'mike'
>
> will
> On Monday 29 September 2003 13:35, [EMAIL PROTECTED] wrote:
>> After I execute a command like
>>
>> CREATE TYPE employee_wage_journal_sum AS (supplier_pk integer,
>> employee_pk integer,
>> hourly_dollars double precision,
>> annual_dollars double precision);
>>
>> where
On Tue, 30 Sep 2003, Angel Todorov wrote:
> Hello, sometimes I get a strange error from postgresql when I try to
> connect using ssl to the server:
>
> LOG: parse_hba: invalid syntax in pg_hba.conf file at line 46, token
> "hostssl"
> FATAL: Missing or erroneous pg_hba.conf file, see postmaste
Angel Todorov writes:
> LOG: parse_hba: invalid syntax in pg_hba.conf file at line 46, token
> "hostssl"
It looks as though your server was not compiled with SSL support.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: e
Bjørn T Johansen writes:
> I run the following SQL before updating one table:
>
> "lock table tablename"
>
> but when I try do update the same table later on, the lock table command
> just hangs (i.e the table is already locked).
> It was my understanding that this lock was removed when I call com
Let's assume I have a table like so:
CREATE TABLE employees (
employeeid text not null,
name text not null
);
CREATE INDEX i_employees ON employees(lower(name));
Let's also assume that the lower() function is computationally
expensive. Now if I have a query like:
SELECT lower(name)
FROM emplo
It looks like it was a one time happening... I restarted the database
and then tried again and then it all worked like a charm Hmmm
BTJ
On Tue, 2003-09-30 at 12:33, Bjørn T Johansen wrote:
> I run the following SQL before updating one table:
>
> "lock table tablename"
>
> but when I try
I run the following SQL before updating one table:
"lock table tablename"
but when I try do update the same table later on, the lock table command just hangs (i.e the table is already locked).
It was my understanding that this lock was removed when I call commit or do I have to explicitly unl
dblasby wrote:
> strk wrote:
> > Dave, I made no special 'unite' code, just sql create command:
> > CREATE AGGREGATE unite (
> > sfunc = GeomUnion,
> > basetype = geometry,
> > stype = geometry
> > );
>
> Hum - this shouldnt do anything.
>
> The aggregate should have "null" as its ini
Oki, I will check it out
Thx! :)
BTJ
On Tue, 2003-09-30 at 11:24, Richard Huxton wrote:
> On Tuesday 30 September 2003 09:50, Bjørn T Johansen wrote:
> > On Tue, 2003-09-30 at 10:42, Richard Huxton wrote:
> > > So - your rule is something like:
> > >
> > > For some block of times...
> > >
On Tuesday 30 September 2003 09:50, Bjørn T Johansen wrote:
> On Tue, 2003-09-30 at 10:42, Richard Huxton wrote:
> > So - your rule is something like:
> >
> > For some block of times...
> > IF max(my_time) - min(my_time) > 12 hours
> > THEN sort "through midnight"
> > ELSE sort "naturally"
>
> Why can't you just take my word for it, this is the way it should be
> sorted
He *does* take your word that this is the way it should be
sorted. But without knowing WHY this is the way it should be
sorted it is hard to deduce an algorithm for doing so.
What you probably need to do is sort th
On Tue, 2003-09-30 at 10:42, Richard Huxton wrote:
> So - your rule is something like:
>
> For some block of times...
> IF max(my_time) - min(my_time) > 12 hours
> THEN sort "through midnight"
> ELSE sort "naturally"
>
> Which is what Tom said (I was wondering where he got his 12 hours fro
Hello, sometimes I get a strange
error from postgresql when I try to connect using ssl to the server:
LOG: parse_hba:
invalid syntax in pg_hba.conf file at line 46, token
"hostssl"
FATAL: Missing or erroneous pg_hba.conf
file, see postmaster log for details
The contents of the pg
On Tuesday 30 September 2003 09:00, Bjørn T Johansen wrote:
> Why can't you just take my word for it, this is the way it should be
> sorted
I'm happy to take your word, but until I can figure out what rules you're
using I can't suggest anything. You clearly know what you want, but I can't
ge
Why can't you just take my word for it, this is the way it should be
sorted
The reason I know this, is because the timespan, as I have mention
before, from first record to last record is always less than 12 hours.
i.e the span from 0200 to 2200 is 20 hours, i.e. 2200 comes before 0200!
BTJ
31 matches
Mail list logo
