On 1/27/07, Michael Fuhr <[EMAIL PROTECTED]> wrote:
On Thu, Jan 25, 2007 at 02:28:38PM -0500, Michael Artz wrote:
> Perhaps my understanding of the 'encode' function is incorrect, but I
> was under the impression that I could do something like:
>
> SELECT lower(e
Perhaps my understanding of the 'encode' function is incorrect, but I
was under the impression that I could do something like:
SELECT lower(encode(bytes, 'escape')) FROM mytable;
as it sounded like (from the manual) that 'encode' would return valid
ASCII, with all the non-ascii bytes hex escaped
t;[EMAIL PROTECTED]> wrote:
"Michael Artz" <[EMAIL PROTECTED]> writes:> Silly little question, but is there something to input/output hex> escaped data into a bytea, alaPQescapeBytea, perhaps? The way you are doing it has multiple problems.
regards, tom lane
Silly little question, but is there something to input/output hex
escaped data into a bytea, ala
CREATE TABLE a (lob BYTEA);
INSERT into a (lob) VALUES ('\x01\x02\x00\x03\x04');
INSERT into a (lob) VALUES ('\x01\x00\x02\x00\x03\x04');
It seems to work (doesn't error), but when selecting the data
Forgot important part ... running on RHEL 4 Update 3 x86_64 using the
8.1.3 PG distributed in the RH Web Application Beta.
SELECT version()
PostgreSQL 8.1.3 on x86_64-redhat-linux-gnu, compiled by GCC
x86_64-redhat-linux-gcc (GCC) 3.4.5 20051201 (Red Hat 3.4.5-2)
-Mike
I'm trying to partition my table on the first octet of an ip4 column
and can't seem to get the planner to do the constraint_exclusion. The
following SQL (copied by hand):
CREATE TABLE a (ip ip4);
CREATE TABLE a_1 ( CHECK (ip <<= '1.0.0.0/8' ) INHERITS(a);
CREATE TABLE a_2 ( CHECK (ip <<= '2.0.0.0
Use 'EXECUTE' to dynamically build SQL:http://www.postgresql.org/docs/8.1/interactive/plpgsql-statements.html#PLPGSQL-STATEMENTS-EXECUTING-DYN
-MikeOn 13 May 2006 14:15:52 -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> wrote:Using PL/PGSQL, I am trying to create a procedure to display the count
of
> The postmaster log might have something enlightening ...
hmm, perhaps. I had a couple of these messages in there:
postgresql-2006-05-14_105843.log:2006-05-14 11:01:34 LOG: could not
receive data from client: No connection could be made because the
target machine actively refused it.
however
I thought I'd be clever and use the cygwin 'psql' client to connect to
the Windows native PostgreSQL 8.1.3 running on the same box, since the
the cygwin port feels more like home (keybindings). Unfortunately, I
get the following message when connecting (after about a minute):
$ psql -h 127.0.0.1
I highly suggest reading the manuals, specifically the first link to the windows installation instructions:
http://pginstaller.projects.postgresql.org/faq/FAQ_windows.html
http://www.postgresql.org/docs/8.1/interactive/index.html
You are getting an error because either you entered in the wrong pas
How do you know that the database exists? If you load up psql, and
then \c dspace, does it let you? If you \l in psql, do you see dspace?On 5/2/06, Christo Romberg <[EMAIL PROTECTED]
> wrote:
Hi!I have some problems with PostgreSQL v8.1.3.My system is Windows XP Professional Edition.An error occu
> -Disk 2: If the transaction log dies, all changes since the last> checkpoint are lost, right? Again, if I set up an empty pg_xlog
> directory somewhere else, the DB should run just fine, right?No, because there's no way to know what state the data pages are in.Data may have made it to disk, may
(Sorry if this gets posted twice ... forgot that the list doesn't like new, unregistered email addresses)
I'm setting up PG, and am curious about the failure scenarios of
Postgres with respect to crashed disks. In a given Postgres
installation across many disks, which sections of Postgres can fai
13 matches
Mail list logo
