)
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c89101f10402127211624!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
the query.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c8675d010409863511634!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
. It's about
half-way then I guess.
b) How much space will be shrank at the time vacuum full finishes?
According to the above up to 27GB (probably less), not counting the index bloat
you're generating by running vacuum full.
Alban Hertroys
--
Screwing up is an excellent way to attach something
instead of psql.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c7c9a6510401193214009!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
btw, if you're worried about disk space?
I can take a dump_file but I can't restore it. Is there any other way to
restore compressed data ?
Didn't you read the man page for the --compress option? You can just pipe your
dump through gunzip.
Alban Hertroys
--
Screwing up is an excellent way
of Microsoft Visual Nuclear Power Plant Designer.
On 27/08/10 07:30, Mike Christensen wrote:
I found this tool pretty helpful for validating my architectural decisions..
http://www.howfuckedismydatabase.com/
Interesting tool :)
Alban Hertroys
--
Screwing up is an excellent way to attach something
again)? Or mouse scrolling when using the scroll wheel over a piece of
user-interface that doesn't have focus (Answer; install katmouse)? Or basic
file-system performance? Or detaching a USB-keyboard without halting the OS for
a second?
/Windows-rant
Alban Hertroys
--
If you can't see
||'.'||relname
^
HINT: No operator matches the given name and argument type(s).
You might need to add explicit type casts
There's nothing before the first concat operator ;)
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM
internally as well (at least shared
memory), so maybe it's possible to use some of the internal mechanisms. I have
no idea whether that's possible or at all advisable, I'm sure someone (probably
Tom) will chime in regarding that.
Cheers!
-Original Message-
From: Alban Hertroys
need(ed) to allow access to it somehow for your jails.
Or you're running into issues sharing the same shared memory across multiple
jails (and the base system) maybe?
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c67aeef967631104912678
transaction, you'll probably need to use a separate connection for the logging.
I think LISTEN/NOTIFY may come in handy there.
end;
end;
$BODY$
LANGUAGE 'plpgsql' VOLATILE
COST 100;
ALTER FUNCTION test.log_and_stop(text) OWNER TO postgres;
Alban Hertroys
--
If you can't see the forest
On 12 Aug 2010, at 16:04, Torsten Zühlsdorff wrote:
Ok, next round. I just have truss as an option, because strace didn't work at
my AMD64. Hope its helpfull:
I haven't used it yet, but I've heard good things about DTrace, which is
apparently in base these days.
Alban Hertroys
--
Screwing
, as it leaves the item names in
tact.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c5e6ee4286211665369939!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
other ideas howto solve this problem?
I think cursors are what you're looking for. Start reading from:
http://www.postgresql.org/docs/8.4/interactive/sql-declare.html
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM
has to use one of their real-time engines for
telecommunication, where data-integrity apparently isn't considered critical.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c5d30a7286211834955988!
--
Sent via pgsql
each value in application by some scale
isn't nice, too.
Most people don't use float for monetary values.
Have a look at the NUMERIC type:
http://www.postgresql.org/docs/8.4/interactive/datatype-numeric.html
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll
Postgres does seem to be on the rise. There's still a ways to go
to make potential users aware of its existence though.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c52a8c2286211512421222!
--
Sent via pgsql-general
done so
for PostgreSQL, and some even wrote about it, but to make up for the difference
we need to do a lot more writing of articles than those MySQL folks.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM
:
http://www.postgresql.org/docs/8.4/interactive/xfunc-volatility.html
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c52ae01286211819977167!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
: (campaign = 42)
Nothing wrong here either.
Total runtime: 2209.869 ms
(10 rows)
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c4f43dc286213192919587!
--
Sent via pgsql-general mailing list (pgsql-general
user, but you still connect with the user who created the
database.
REVOKE UPDATE ON station FROM afsugil;
And then you revoke rights from that user instead of from the test user.
Effectively you're not using the 'test' user at all in your script. Was that
intended?
Alban Hertroys
--
Screwing
index is in trouble.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c4abfcd286214416410229!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
you're interested. I'm not sure how easy that would be to upgrade to the
builtin version once you get to 8.3 or newer though...
Thanks for helping out a n00b.
You're welcome, we've all been there.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see
which columns you left out? ;)
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c4ac805286212004583493!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
?
--
t
(1 row)
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c49503f286213027486771!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
to the connection. You can't have multiple transactions
running in parallel on one connection.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c482748286211410335719!
--
Sent via pgsql-general mailing list (pgsql-general
result available after the insert into the parent table
finishes. Probably not though, seeing you have to return NULL at the end of
that before INSERT trigger...
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM
be nicer to have, but I don't see any
straightforward way to unnest your CSV data in such a way that you could apply
one to it.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c45c239286211821273955!
--
Sent via pgsql-general mailing list
| 1
(1 row)
Sure, you'll have to join with the with-query to get any meaningful results,
but if there are any complicated calculations in that query, won't they be
calculated just once - like you intended?
If not, I think we're all failing to see the point you're trying to make.
Alban
the PG_DATA directory is supposed to be, and
according to initdb it is there - which is why I think you don't have access.
It looks like postgres failed to stop (probably due to lack of permissions for
you to do so). Is it indeed still running?
Alban Hertroys
--
Screwing up is an excellent way to attach
from a rule or trigger.
OTOH, if you have a trigger anyway, you can move the checks in there as well.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c3dff91286211140418644!
--
Sent via pgsql-general mailing list
to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c39a024286213416620622!
--
Sent via pgsql-general mailing list (pgsql-general
site_archeological? Or if arquelogy is
Spanish or Portuguese, shouldn't it be arquelogical?
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c370742286211218711353!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
inheritance you'll have to redefine the foreign key constraint
on each child table, as the FK constraint won't be inherited.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c376755286211334030252!
--
Sent via pgsql-general
.
I'm just saying, be careful what you're parsing there ;)
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c359d9f286212106016419!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
.
After putting a bunch of RAISE
NOTICEs in my triggers it would appear as though the former scenario is
happening but I'm not 100% sure.
I'm quite confident it does.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM
rule. For example the UPDATE could
be done when WHERE email = 'X' or WHERE id = 'Y' .
Question: How can I deal with this?
In the WHERE-clause you use the columns from the OLD record that uniquely
identify that record.
Alban Hertroys
--
Screwing up is an excellent way to attach something
it to identify
the records for the update. Whether that PK uses a simple unique index or a
composite unique index doesn't matter at all either.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c33391e286211703874864!
--
Sent via pgsql
time include the duration of the invoked
triggers?
It does time how long it takes for the command to complete. Since I'm quite
sure triggers fire and execute sequentially, the command cannot complete until
all trigger procedures finished executing. So, yes.
Alban Hertroys
--
If you can't see
data wasn't inserted while later data depends on it, causing
a constraint violation.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c249b98286211487176982!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
all records.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c2321f5286211760940954!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
improvements to that in later
versions.
Another approach would be an index on (email_sender, email_msg_id) - that would
particularly help the second query and it shouldn't hurt queries on just
email_sender much.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees
inheritance for duplicates? If you're
querying the master table without the ONLY keyword then you'll see the data
from the child tables as well.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c1752e1286215067983550!
--
Sent via pgsql-general
because Windows isn't very good at
multi-processing and Postgres runs as multiple processes.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c17598b286211489720513!
--
Sent via pgsql-general mailing list (pgsql
built with
libreadline? Without it you don't get TAB-completion, that would be a nuisance!
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c160039286219954085656!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
On 14 Jun 2010, at 12:14, Schwaighofer Clemens wrote:
On Mon, Jun 14, 2010 at 19:10, Alban Hertroys
dal...@solfertje.student.utwente.nl wrote:
On 14 Jun 2010, at 2:02, Clemens Schwaighofer wrote:
Right now I added two simple wrappers in my .psqlrc
\set shsh 'SHOW search_path;'
\set
to a server to
restore it, rather than something that saves directly to file, or
passes it through a pipe?
That sounds quite a bit like replicating the DB to a warm standby, is that what
you're after? There are several solutions for that.
Alban Hertroys
--
If you can't see the forest
to accomplish. I'd think pg_dumpall,
pg_restore and psql would be useful too.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c162b52286211582820103!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
On 14 Jun 2010, at 22:22, Scott Marlowe wrote:
Is there are good reason to go to Windows instead of a new BSD system?
Windows is a known mediocre performer for postgres.
I was wondering that too. I assume the good reasons wear ties.
Alban Hertroys
--
If you can't see the forest for the trees
) and links to two different code
pages listing the characters therein.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c0a0c3a10151431365867!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
back to a working system - be aware though that you probably were already
having issues with displaying some data correctly.
-Original Message-
From: Alban Hertroys [mailto:dal...@solfertje.student.utwente.nl]
Sent: Saturday, June 05, 2010 1:35 AM
To: Wang, Mary Y
Cc: pgsql-general
dropping the FK
constraints.
Quite a bit of trouble to go through to replace one index.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c08c8841015795493!
--
Sent via pgsql-general mailing list (pgsql-general
of these gives the same error message:
CONTEXT: ERROR
CODE: 42804
MESSAGE: cannot assign non-composite value to a row variable
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c0908b610152006515388!
--
Sent via pgsql-general mailing list
.
I usually find the psql prompt more efficient to work with than, for example,
pgadmin. But I'm a typical command line user; What's efficient for one may not
be for someone else.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM
by f.finance_company_name, b.brokerage_name, bc.quote_no
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c07a96310151389715979!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
(for example an ils performed in 0.3 s will goes down to less
than 0.1 s when reindexing has been made).
There are cases where reindexing shows a performance improvement over just
analysing a table, but the above (only inserts) shouldn't be one of them.
Alban Hertroys
--
Screwing up is an excellent
with that.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c0599a810154434717690!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
. Either escape
them or turn on standard_conforming_strings.
That said, if you're having this problem your queries are probably vulnerable
to SQL injection too, they're certainly not parameterised or Postgres would
have done the escaping for you.
Alban Hertroys
--
If you can't see the forest
the '/' at the start of the
line.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c00decd10151812910245!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
/Global_Interpreter_Lock
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bff996b10419162611771!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Services dialog, however
using pgAdmin I can start the service and connect to my database, run queries
etc.
Sorry, can't help you there - I rarely use Windows.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bffe51f10216640413027!
--
Sent
enough to declare those lists only once
otherwise. The concept remains though.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4c00531510211149731783!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
...RETURNING
returns - very convenient if the value you inserted was generated somehow (by a
sequence for example).
Since you can also UPDATE some column using a generated value, it'd make sense
if it would behave the same way.
Alban Hertroys
--
Screwing up is an excellent way to attach something
.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bff0ec010411146380094!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
, as the rows you commit here
still aren't allowed to be visible to other transactions and so both versions
of the rows need to be kept around until the outer transaction commits. It's
not going to save you any space.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees
with it?
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bfba33510414354318240!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
in size
So I guess your large object is too large.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4bf6617510414104348269!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
that threw me off, hadn't realised you were referring to a dump file
there.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4bf67a7e10411591919641!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
might want to
give us some context, like the actual error message and from what command you
got that for example.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4bea7ae010413218958980!
--
Sent via pgsql-general mailing
' for a table
To: Alban Hertroys dal...@solfertje.student.utwente.nl
Cc: pgsql-general@postgresql.org
Date: Wednesday, 12 May, 2010, 10:57
no it is not slony related.
It is a postgresql problem.
my original post:
http://archives.postgresql.org/pgsql-general/2010-05/msg00402.php
--
Sent via
palloc.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4beadfeb10411880534263!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
of like?
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4be7d6ec10411051620847!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
(dspam) catches
about that much in a weeks time for my account alone. Without a total or a
starting date its just a meaningless number.
Do you have any influence on what it prints under your messages?
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see
up with all kinds of
dummy-data in your client application, but you also don't want to remove any
constraints that guarantee sensibility of the data in those tables.
None of these solutions are pretty. It should be quite a common problem though,
how do people normally solve this?
Alban Hertroys
the useful ltree operators for
trees.
I recall from the docs that you can create arrays of ltrees. It has some
special operators for that. I couldn't figure out what the use case for those
ltree-arrays was (the docs are rather sparse), but it might just be what you're
looking for.
Alban
On 10 May 2010, at 21:24, Christoph Zwerschke wrote:
Am 10.05.2010 11:50 schrieb Alban Hertroys:
On 10 May 2010, at 24:01, Christoph Zwerschke wrote:
select * from b join a on b.txt like a.txt||'%'
I feel there should be a performat way to query these entries,
but I can't come up
be surprised if your different types of orders
originate from different locations in the user interface, for example.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4be6782910411440911937!
--
Sent via pgsql-general
SELECT fields FROM parritioned_table WHERE primarykey = constant;
he says the planner will go straight to the correct partition.
i haven't confirmed this for myself.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bdc08fc10416246414315
On 1 May 2010, at 12:56, Alban Hertroys wrote:
You could argue that some logic could be added to the handling of prepared
statements to insert query-subplans depending on what data you use for your
parameters, but then you're moving back in the direction of unprepared
statements (namely
tables that translate that gibberish to human readable stuff. You could go
further and make those views updatable (by means of a few rules), but then you
run the risk that colleagues start to hug you...
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM
application, so combining the two and do that only once may be preferable. If
you're thinking of going that way I'd suggest FreeBSD or Solaris, but Linux is
a popular choice (as is Windows, for that matter).
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling
of assigning more than a 32-bit number for the amount of shared memory? Are you
running in some kind of 32-bit compatibility mode maybe (PAE comes to mind)?
That said, I haven't used Windows for anything more serious than gaming since
last century - I'm not exactly an expert on its behaviour.
Alban
were referring to, so I deleted the remainder. Top-posting
is considered bad form in mailing-lists.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bd6e4f110411684215286!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
)
SELECT \$1, \$2, \$3
EXCEPT
SELECT id, txid, txtime
FROM changelogtest
WHERE id = \$1
AND txid = \$2
AND txtime = \$3;
ENDQUERY
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4bd3201310412109115467
select (id, txid, txtime)
^^^--- 1 column, a row-type containing (int, int,
timestamp)
from changelogtest
where id=5;
ERROR: each EXCEPT query must have the same number of columns
LINE 2: except select (id, txid, txtime)
Alban Hertroys
--
If you can't see the forest
AND txtime = \$3;
ENDQUERY
You need to remove the braces from the query in your trigger too, they change
the meaning of the query. You use brackets in this way if you need to reference
fields from a composite type.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling
On 19 Apr 2010, at 20:26, cojack wrote:
Alban Hertroys wrote:
It would help if you'd show us what result you expect from ordering the
above.
Most people would order this by path I think. However that doesn't match
your sort column and I can't think of any method that would give results
solution, I just can't get my mind around it right now.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4bcdf5a610412270627163!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
moved into Colors as well?
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4bcdf97810413554942613!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
of any method that would give results in such an
arbitrary order as you seem to be specifying - unless you set it by hand like
you do.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bcc9b1e10415135793547!
--
Sent via pgsql-general mailing
On 13 Apr 2010, at 2:36, John R Pierce wrote:
Alban Hertroys wrote:
Storing those passwords encrypted on the client side seems the proper way to
deal with this issue. IMHO, time working on that is better spent than time
trying to prevent .pgpass files from working.
afaik, the .pgpass
the other way
around.
Since your function has smallint as one of its parameter types the database
can't cast the smallint up to an int like it would normally do in such cases as
the function doesn't accept integer values for that parameter. PG can't do much
but throw an error.
Alban Hertroys
with when installed on Windows.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4bbbc65910411225214359!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
from. You
probably meant to put some constant values there or results from another table.
select wordwrap83('fdgdf',10)
^^
These values for example.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM
with that, but in
your situation I think the postgres superuser may be a bit too powerful. You're
probably better off creating a non-superuser role for this purpose.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bb4688c10419781048118!
--
Sent
with...
It's most probably a problem in your client or your connection library, other
people are using temp tables without a problem. Temp tables are not exactly a
new feature either.
Alban Hertroys
PS. Considering the way you quote your mails you seem to have an absolutely
terrible mail client. If you
.pgpass files from working.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4bb47e3510419564511622!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
persists, maybe you could post your function somewhere. As it's
apparently a rather long function, can you strip it down to something that
still causes it to run out of memory but that will be a bit easier for the
people on this list to wade through?
Alban Hertroys
--
If you can't see the forest
,
Birgit.
On 01.04.2010 13:27, Alban Hertroys wrote:
On 1 Apr 2010, at 12:22, Birgit Laggner wrote:
Dear list,
I have some data (big size) and I've written a long function in pl/pgsql
which processes the data in several steps. At a test run my function
aborted because of memory
that is being defined by the data it's
running over (eg. a window defined by the length of an accumulated line of
text).
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4bb1d23410411798520618!
--
Sent via pgsql-general mailing list (pgsql-general
601 - 700 of 1292 matches
Mail list logo
