On 13 Oct 2001 at 0:41, Dan Langille wrote:
> I'm looking at giving other developers access to a development database,
> but I want to impose tight restrictions on who can do what. One thing I
> want to investigate is the ability to let them execute stored procedures
>
I'm looking at giving other developers access to a development database, but I want to
impose
tight restrictions on who can do what. One thing I want to investigate is the ability
to let them
execute stored procedures but not view them.
Is this pretty standard stuff?
--
Dan Langill
: line 1, CopyFrom: Fail to add null value in not null
attribute name
lost synchronization with server, resetting connection
Without single-stop, it works fine:
$ psql fp2migration < users.txt
$
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
-
rder to fix.
$ psql fp2migration < fp2migration.sql.timestamp.library
[snip]
ERROR: copy: line 2537, Bad timestamp external representation 'current'
lost synchronization with server, resetting connection
^C
Any clues as to what will fix this problem?
--
Dan Langille
The FreeBS
On 23 Feb 2002 at 12:19, Peter Eisentraut wrote:
> Dan Langille writes:
>
> > $ psql fp2migration < fp2migration.sql.timestamp.library
> > [snip]
> > ERROR: copy: line 2537, Bad timestamp external representation 'current'
> > lost synchroni
On 23 Feb 2002 at 0:59, Dan Langille wrote:
> I'm importing the data from my 7.1.2 database into 7.2 and I've found a few
> problems.
[snip]
> $ psql fp2migration < fp2migration.sql.timestamp.library
> [snip]
> ERROR: copy: line 2537, Bad timestamp external rep
a
timestamp field. I corrected the data, exported, and imported into 7.2.
All went well[1].
Now my concern is how the value 'current' found its way into a timestamp
field I'm looking at the application.
thank you.
[1] - I did have to manually modify the pg_dump ou
On 23 Feb 2002 at 14:28, Dan Langille wrote:
> On 23 Feb 2002 at 11:22, Sean Chittenden wrote:
>
> > > I've just been able to confirm that 7.1.2 can import the above data. My
> > > plans for 7.2 are now on hold while I try to find a way to get 7.2 to
> &
On 23 Feb 2002 at 14:50, Tom Lane wrote:
> "Dan Langille" <[EMAIL PROTECTED]> writes:
> > now I'm getting: ERROR: SearchSysCache: Bad cache id 27
>
> I believe we've seen this from trying to load a 7.1 plpgsql.so
> into 7.2.
Tom! Well done.
g
the Belarus/Russia game... ;)
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
*old* installation's plpgsql.so --- am I not right?
You are correct.
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appr
On 27 Feb 2002 at 9:30, Chris Pesko wrote:
> Can I put transactions and cursors into functions?
No.
> As soon as I put BEGIN;
> and COMMIT; wrapping an insert statement within a function, I get errors.
> Do these programs need to reside outside of the database?
AFAIK, yes.
--
On 1 Mar 2002 at 11:15, Brett W. McCoy wrote:
> I'm guessing it's coming from the server that hosts [EMAIL PROTECTED] --
> you're stuff isn't coming with any attachments on my system (also Linux).
My virus warning originated from [EMAIL PROTECTED]
--
Dan Langill
On 1 Mar 2002 at 11:46, Brett W. McCoy wrote:
> On Fri, 1 Mar 2002, Dan Langille wrote:
>
> > On 1 Mar 2002 at 11:15, Brett W. McCoy wrote:
> >
> > > I'm guessing it's coming from the server that hosts
> > > [EMAIL PROTECTED] -- you're stuff i
identify the duplicate constraints.
$ pg_dump -s > fp2migration.ddl
$ grep "CREATE CONSTRAINT TRIGGER" ~/fp2migration.ddl > constraints.txt
$ cat constraints.txt | sort | uniq > constraints.sorted.txt
$ wc -l constraints.txt
93 constraints.txt
$ wc -l constraints.so
On 2 Mar 2002 at 10:19, Dan Langille wrote:
> CREATE CONSTRAINT TRIGGER "" AFTER INSERT OR UPDATE ON "ports"
> FROM "categories" NOT DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE
> PROCEDURE "RI_FKey_check_ins" ('', 'ports&#x
On 2 Mar 2002 at 11:09, Stephan Szabo wrote:
> On Sat, 2 Mar 2002, Dan Langille wrote:
>
> > On 2 Mar 2002 at 10:19, Dan Langille wrote:
> >
> > > CREATE CONSTRAINT TRIGGER "" AFTER INSERT OR UPDATE ON "ports"
> > > FROM "categories&q
et the same trigger names
> after the restore as the ones in the dump file comments. You may have to
> look in the system table for the actual current trigger name for the
> triggers with those arguments.
There was no restore. I did the dump in order to find the duplicates.
Then used
fy the version. The applications knows what
version it can run with. If it finds an older version, it reports this ot
the user and suggests they upgrade their database.
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---(end of bro
to get the time it takes to perform a query?
I was told about this last night: With 7.2, explain analyze
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/sql-
explain.html
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---
oing that I starting thinking about triggers. Checking the
documentation, I don't see a similar feature for triggers. I'm guessing
that triggers do not suffer from the same problem as that which prompted
the original post.
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org
nabled in postgre[sql].conf. I know
only because I asked the same question a few days ago:
http://www2.ca.postgresql.org/users-lounge/docs/7.2/postgres/runtime-
config.html
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---(end of br
On Wed, 3 Apr 2002, Trevor Astrope wrote:
> I restored a 7.1.3 database to another machine which seems to have went
> fine. However, the data on the disk is less than the original machine...
> There is only 6.5GB in pgsql/dta/base on my test machine and the same
> directory on the production mach
ormance is
> > slowed down by a factor of 20 or 30 For exemple :
> > select timestamp,value
> > from measure
> > where timestamp(now() - '1 hour'::interval)
Try where timestamp(now() - '1
hour'::interval)::timestemp.
--
Dan Langille
The Fre
On 10 Apr 2002 at 10:44, JX wrote:
> Le Wed, 10 Apr 2002 09:27:09 -0400
> "Dan Langille" <[EMAIL PROTECTED]> me disait que :
>
> > On 10 Apr 2002 at 9:13, JX wrote:
> >
> > > Le Wed, 10 Apr 2002 09:06:55 -0400
> > > "Dan Langille&q
On 10 Apr 2002 at 10:55, Dan Langille wrote:
> If there is an index on that field, casting to a timestamp may help the
> optimization. Therefore I suggested that it be tried.
And using "explain" will show the plan for that command. I recommend
using that too.
--
Dan Lang
ure, put unique constraints on business values if you want.
Just don't make them a primary key or a foreign key.
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---(end of broadcast)---
TIP 1: subscribe and unsubs
g a 34KB messages.
thanks.
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED]
at
<http://www.freebsddiary.org/postgresql-7.2.php>
I recommend keeping a 7.1 box installed and running until you get 7.2
running the way you like it.
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---(e
to "beat me to it".
> In any event, inserting then using currval() is the standard practice
> around here, and it works great. Nothing fishy at all here, nothing to see,
> move on.
Why is that "less risk"?
--
Dan Langille
The FreeBSD Diary - http:/
On 6 May 2002 at 12:43, Joel Burton wrote:
> > -Original Message-
> > From: Dan Langille [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, May 06, 2002 12:41 PM
> > To: Joel Burton
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: [ADMIN] SERIAL Field
> >
his
table. All went well and I had my database back and running.
I ran a VACUUM ANALYZE. No problems were reported. Then I ran a VACUUM
full ANALYZE, which went fine.
Any suggestions/recommendations/comments?
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practica
o transaction ID
wraparound.
Read 8.2.2. Updating planner statistics
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
version which
changes daily. It's really only for people who are developing FreeBSD.
It frequently contains works in progress and experimental changes.
see <http://www.freebsd.org/handbook/current-stable.html>
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.o
On 13 May 2002 at 8:20, Brian McCane wrote:
> On Sun, 12 May 2002, Dan Langille wrote:
>
> >
> > On 12 May 2002 at 12:49, Brian McCane wrote:
> >
> > > I am on FreeBSD 5.0.
> >
> > There is a reason why you must be on 5.0? That is not recommended f
27;test');
nextval
-
3
(1 row)
testing=# select nextval('test');
nextval
-
4
(1 row)
testing=#
Then back to the other window:
testing=# select currval('test');
currval
-
1
(1 row)
testing=# select nextval(&
On 10 Oct 2002 at 9:46, Reiner Dassing wrote:
> To upgrade to PostgreSQL 7.2.3 there is an 'initdb' necessary.
This caused me to ask around off-list. An initdb is required only if
you are upgrading from from pre-7.2.X.
--
Dan Langille
I'm looking for a
On Tue, 22 Oct 2002, Bruno Wolff III wrote:
> In 7.3 you can get a pretty good handle on this. The database owner can
> restrict who can create schemas and schema owners can control who can
> create objects in that schema.
Will I be able to give people the right to execute a function, but not
vie
On Wed, 23 Oct 2002, Tom Lane wrote:
> Dan Langille <[EMAIL PROTECTED]> writes:
> > Will I be able to give people the right to execute a function, but not
> > view it?
>
> Write it in C. Short of that, you're asking for unenforceable
> restrictions on the ab
On 22 Nov 2002 at 19:07, dima wrote:
> i wrote a script in perl which dumps all the DBs but template*
> i can mail it to you if you wish
Why not post it to the list? That way it's available for everyone.
I'm guessing it'll be less than 2K or so...
--
Dan Langille : ht
nsequently do not think of them when
backups are required.
> I'll be working on it some more and will share what I come up with.
I'm sure it will be added to the contrib directory.
--
Dan Langille : http://www.langille.org/
---(end of broadcast)
hings about hash
> indexes in PostgreSQL.
No, don't use them. I didn't get any performance increase out of
them. Does your experience show poor btree results?
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 1: subsc
If you're concerned, why not try a partial index?
FWIW, partial indexes didn't help for my distributions. But btrees
were satisfactory.
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
999.
> How to do this change?
http://www.postgresql.org/idocs/index.php?functions-sequence.html
Look for setval
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
x27;t know, but I'm sure it can be done.... someone else will
know.
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
ript:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/databases/postgresql7/file
s/502.pgsql
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
ere's nothing wrong with that
> I lean toward #2 but wanted to see if there was a preferred standard
> or ano= ther possibility that I am overlooking??
I would recommend #2.
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
ml:
pg_dump makes consistent backups even if the database is being used
concurrently.
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
regards, tom lane
>
> PS: a wild-*ss guess: 7.0 wasn't too clean in handling OIDs above 2
> billion; is it possible your pg_language OID for plpgsql is over 2G?
Followed by another wild guess. Could the path be the problem?
Looking at my notes (http://www.freebsddiary.org/p
ver. Can someone give me some insight into this?
You should seek someone who provides PostgreSQL out-of-the-box. I
did a search on google.com yesterday for postgresql and web host and
found a few such places.
--
Dan Langille : http://www.langille.org/
---
not null
default 'current_timestamp',
- remove key name from foreign keys
alter table element_pathnames
add foreign key FK_ELEMENT__REF_11730_ELEMENT (element_id)
references element (id) on update cascade on delete cascade;
Has anyone already done this?
--
Dan
On 19 Dec 2002 at 8:57, Dan Langille wrote:
> The two remaining problems are:
>
> - default values are always enclosed in single quotes (') which is
> fine for character fields but not for anything else.
>
> e.g
>
> create table security_notice
> (
&g
On Mon, 23 Dec 2002, Tom Lane wrote:
> "Rob Abernethy IV" <[EMAIL PROTECTED]> writes:
> > I cannot get the postmaster to start up in SSL mode. I receive the following
> > error:
> > bad permissions on private key file (/var/lib/pgsql/data/server.key)
>
> > -rw-r--r--1 postgres postgres 32
On Mon, 23 Dec 2002, Jie Liang wrote:
> Forgive me this silly question:
> at ftpsite there always a md5 file followed the tarball file(e.g.)
> postgresql-7.3.1.tar.gz
> postgresql-7.3.1.tar.gz.md5
> what is this md5 file for? how to use it?
> I guess it's a cksum, but I am not sure.
It is used to
On Mon, 23 Dec 2002, Bruce Momjian wrote:
> Patch attached. Will appear in 7.3.2 and 7.4.
Looks good to me. Thank you.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Mon, 23 Dec 2002, Bruce Momjian wrote:
>
> PostgreSQL is designed to _not_ require root access, so we just make
> everything owned by the install user. I don't see how group checks can
> help there. Also, there is no postgres group, at least by default, and
> no special handling based on grou
arded message ---
Feedback on this solution is appreciated.
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On 7 Jan 2003 at 10:29, Tom Lane wrote:
> "Dan Langille" <[EMAIL PROTECTED]> writes:
> > I am forwarding this on behalf of [EMAIL PROTECTED] who is at a client
> > site and cannot email.
>
> > I did a search and found a mail stating that its possi
58 matches
Mail list logo
