The security documentation available in the official documentation is
rather sparse. Is there a more detailed document I should be aware of?
As an example, I'd like to prevent a a user from being able to get a
list of existing databases. Presumably, I can limit access to various
system catalogs to
Are there any data access issues (as opposed to data visibility issues)
you are having?
No, It's just that in a hosting situation where each customer has a
database of their own, they need to be boxed in somehow. In the event
of an application bug allowing raw sql to be executed, it's not
appropri
I'm going to be working with some rather large datasets and I want to
evaluate the effects of normalization/denormalization on disk space. Is
there a simple way to find the size on disk of a specific database? To
do so with the operating system is rather crude, since it know nothing
about what prop
It occurs to me that I don't know how to define unsigned integer
datatypes. I'm making a schema to describe network packets and I need
columns to contain values from 0-255, etc.
I can't seem to find any documentation on this. What's the best prectice for this situation?
You can use a signed type with a CHECK constraint to restrict thecolumn's value to positive integers.
The sign doesn't concern me. I am storing a value that is unsigned and
16 bits wide natively. I'll have to just use an int4 and waste twice
the space I actually need.
google for postgresql_autodoc-1.21
On 10/18/05, Dann Corbit <[EMAIL PROTECTED]> wrote:
I use ER/Win for that. There are some other tools too. Search thearchives.> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-> [EMAIL PROTECTED]
] On Behalf Of Bruno Cochofel> Sent: Tu
Are there known limits to how many rows can be inserted by one
transaction, or does that just reflect the already documented row,
table and database limits?
Due to application requirements, I need to implement a rounding
function that is independant of the baked-in rounding functionality.
I'd prefer to do it in plpgsql for maximum portability.
To do this, I'll need to sequentially walk through the digits of an
arbritarily long floating-point number. I
