Hi,
Like many here, I am fairly new to PostgreSQL having been forced to cut my
teeth on M$ SQLServer. My apologies if this is the wrong forum for this
question, please advise if so!
We use a third party application to manage our student population. Part of
the reason we purchased it is
On Tuesday 24 February 2004 16:51, Paul Simpson wrote:
1) If there is a log somewhere showing failed requests, I might be able to
see what the application is trying to do and then figure out a way around
it.
You can log in every query server is executing. You need to enable the
corresponding
Thanks for that! I'll have a look...
Paul Shridhar Daithankar
[EMAIL PROTECTED] 24/02/2004 12:02:30 On Tuesday
24 February 2004 16:51, Paul Simpson wrote: 1) If there is a log
somewhere showing failed requests, I might be able to see what the
application is trying to do and then figure out
Hi,
I need torun the following delete
command ona view table1_v :
"
delete from table1_v where table1_var1=$table1_var1
and table1_var2 not in (select t2.id fromtable2_v
t2,table3_vt3
where t3.vers_id=t2.vers_id and
t3.var3=$var3);
"
I have not been able to figure out how to create
the
hello
is it possible with postgres 7.2 or more, to define a dynamic view.
For example, i have a table with a column 'user'
and i want to define a view which gives infomrations from different
tables but the user has to specifie the 'user' parameter when using a
select to the view
sylvain
Ok, I've done that and it would appear to be a table naming issue...
When I look at the logfile at the point where a table is creates, I get the
following lines (for each table, as far as I can tell, although the third line
only appears for some):-
select relname, nspname, relkind from
On Tuesday 24 February 2004 16:29, sferriol wrote:
hello
is it possible with postgres 7.2 or more, to define a dynamic view.
For example, i have a table with a column 'user'
and i want to define a view which gives infomrations from different
tables but the user has to specifie the 'user'
To all,
It looks like it is the fault of the shutdown script said Sean with
sheepish look on my face
We have to take a look a the scripts, found them on the web, to figure
out what they are doing to cause this.
Sorry for the clutter in your mailboxes.
--sean
waiting for postmaster to shut
Hi to all,
those helped or enjoyedmy english. I waited over the day to give a summary.
your pgsql backend must be able to accommodate the max persistent
connections * the max number of apache daemons.
the php pgsql.max_persistent setting is per apache daemon.
All of your answers where
Hi,
I tried to compile postgresql-7.4.1 on fedora core1, but this
fails with the following error message:
checking for python... /usr/bin/python
checking Python installation directories... /usr/lib/python23.zip
checking how to link an embedded Python application... no
configure: error: Python
Tom,
Let me clarify I was meant shutdown in the context of issuing a stop
against postgres not shutting down the OS. Sorry if I am confusing things.
The scripts we are using to issue start, stop etc for postgres seem to
be causing the issue. I changed the config to use timestamps in the
Hello List,
I have a table that look like this:
create table estad
(nprodfk int, cmes char(6), hmes char(5),
nqty numeric(12,2), nsold numeric(12,5),
ncost numeric(12,2));
It contains this data:
insert into estad
values (25,'200402','FEB04',500,5000,2300);
insert into estad
values
Josué Maldonado wrote:
The problem is I need show the data in this way:
TIPOOCT03NOV03DIC03ENE04FEB04
NQTY 490 360 950 700 500
NSOLD46003900710062005000
NCOST18501760
Sean Shanny [EMAIL PROTECTED] writes:
StopService()
{
ConsoleMessage Stopping PostgreSQL database services
/usr/local/pgsql/bin/pg_ctl stop -D /usr/local/pgsql/data
x=`/bin/ps axc | /usr/bin/grep postgres`
if /bin/test $x
then
set $x
Argh!
This is what my log files look like in pgsql.
How canI grant sequence permissions?
I did a grant all to the user and it still does
this.
ERROR: permission denied for sequence
radacct_radacctid_seqERROR: permission denied for sequence
radacct_radacctid_seqERROR: permission denied
The select statements return different data for
most_commons_vals depending on whether n_distinct is
included in the select clause or not.
I only seem to get the behavior below against int8
columns - but I haven't interated through every
conceivable data type either.
Is this expected behavior or
g == greg [EMAIL PROTECTED] writes:
g A new version of DBD::Pg is about to be released (1.32), and we need
g your help to test it out. If you use DBD::Pg, please download
g and test the latest release candidate. At the very least, running
Has my recent bug report on rt.cpan.org been addressed?
The following SQL:
create table toinherit (
id integer primary key
);
create table leftside (
leftname varchar(64) not null unique
) inherits (toinherit);
create table rightside (
rightname varchar(64) not null unique
) inherits (toinherit);
create table linkthem (
left_id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Has my recent bug report on rt.cpan.org been addressed? I never got
any ack that it was. See
I tried but could not duplicate that bug when it first came out. I
don't know if others have tried it out or not, but if you could test
with 1.32_2
Is this a bug, or a feature? It seems I can't make a column reference
work directly with the table that gets inherited by the others. Neither
can I make a column reference work with a table that *inherits* the
toinherit table. If I can't get this to work, I'll have to revert back
to not using
Will somebody on this list, hopefully the list manager, tell me how to
unsubscribe to this list?
In attempting to sent a request for this to
[EMAIL PROTECTED] , I got this response:
unregister [EMAIL PROTECTED]
The unregister command did not succeed.
The request
Shelby Cain [EMAIL PROTECTED] writes:
The select statements return different data for
most_commons_vals depending on whether n_distinct is
included in the select clause or not.
I only seem to get the behavior below against int8
columns - but I haven't interated through every
conceivable data
Tom Lane wrote:
Hoo, I'm surprised no one noticed this during 7.4 development/testing.
The problem applies for any datatype that requires double alignment,
which includes int8, float8, and timestamp as well as most of the
geometric types. pg_statistic is declared as using type anyarray,
and this
Joe Conway [EMAIL PROTECTED] writes:
anyarray has been defined this way since 7.3 -- any concerns there?
I don't think so --- we weren't trying to use it as an actual column
datatype back then.
7.4 has a problem though :-( ... this is one of the damn I wish we'd
caught that before release ones,
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Has anyone given any thought as to whether dumping and restoring
pg_statistic is worthwhile?
Why? You can reconstruct it with a simple ANALYZE command. Dumping
and restoring would mean nailing down cross-version assumptions about
what it
25 matches
Mail list logo
