Erik Jones <[EMAIL PROTECTED]> writes:
>>> 2008-01-17 21:47:34 CST 7598 :WARNING: relation "table_name" page
>>> 5728 is uninitialized --- fixing
>>
>> If you do a vacuum on the master, do you get the same warnings?
> /me runs VACUUM VERBOSE on the two tables that would matter.
> Nope. What wo
Clodoaldo <[EMAIL PROTECTED]> writes:
> The old server reproduces the behavior of the new one.
Well, that's just weird. Let's see, FC6 has oprofile --- maybe oprofile
measurements on 8.2 and 8.3 on the same box would tell something.
Do you know how to use that? Alternatively, if you could give m
Hannes Dorbath wrote:
Yannick Warnier wrote:
I thought about it, but it's not very portable if you want to ship a PHP
application. But I admit I will fall back to that solution if I cannot
find any other (considering PostgreSQL might be the only open-source
database to offer in-fields arrays any
Yannick Warnier wrote:
I thought about it, but it's not very portable if you want to ship a PHP
application. But I admit I will fall back to that solution if I cannot
find any other (considering PostgreSQL might be the only open-source
database to offer in-fields arrays anyway).
You can use the
Which is exactly why I pointed out that using pg_standby's -k switch
was the more reliable option.
And supposedly even that switch is not needed once we can get to 8.3,
which should be soon. Even the -k switch can be an issue since you
don't really know how many you should keep around.
Da
On Jan 18, 2008, at 4:43 PM, Brian Wipf wrote:
On 18-Jan-08, at 2:32 PM, Erik Jones wrote:
What worries me is, that since I have a verified case of rsync
thinking it had successfully transferred a WAL, the same may have
happened with these files during the base backup. Does that
warning
On 18-Jan-08, at 2:32 PM, Erik Jones wrote:
What worries me is, that since I have a verified case of rsync
thinking it had successfully transferred a WAL, the same may have
happened with these files during the base backup. Does that
warning, in fact, entail that there were catalog entries
2008/1/16, Tom Lane <[EMAIL PROTECTED]>:
> I went through this thread again, and noticed something that no one
> seems to have remarked on at the time: the vmstat numbers near the
> bottom of this post
>
> http://archives.postgresql.org/pgsql-general/2008-01/msg00161.php
>
> show close to 100% I/O
Le vendredi 18 janvier 2008 à 23:10 +0100, Ivan Sergio Borgonovo a
écrit :
> On Fri, 18 Jan 2008 23:01:09 +0100
> Yannick Warnier <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > I've been searching (not very thoroughly, but still) for a way to
> > get Postgres arrays right into PHP arrays, but it
On Fri, 18 Jan 2008 23:01:09 +0100
Yannick Warnier <[EMAIL PROTECTED]> wrote:
> Hello,
> I've been searching (not very thoroughly, but still) for a way to
> get Postgres arrays right into PHP arrays, but it seems that the
> Postgres driver simply doesn't allow that.
What about using a stored pro
Hello,
I've been searching (not very thoroughly, but still) for a way to get
Postgres arrays right into PHP arrays, but it seems that the Postgres
driver simply doesn't allow that.
The only solution seems to use some user-defined functions[1] to split
the result of a query (a string) into a PHP a
Andreas 'ads' Scherbaum wrote:
Have a plperl function that creates connections to all servers in the
cluster (replication partners), and issues the supplied write query to
them, possibly with a tag of some sort to indicated it is a replicated
query (to prevent circular replication).
Have a p
On Fri, 18 Jan 2008, Tom Lane wrote:
pg_controldata already provides this information, no? At least barring
the case of wrong-time_t-size, which we already know we want to fix.
It provides some of it, and I think you could make a case that the text
file format Dave suggested could be prototy
On Jan 18, 2008, at 3:17 PM, Tom Lane wrote:
Erik Jones <[EMAIL PROTECTED]> writes:
I recently started up a server created using PITR (exact detail
below) and received about 125 of these type of errors spanning pages
in about 10 different tables:
2008-01-17 21:47:34 CST 7598 :WARNING: rela
Hello,
On Fri, 18 Jan 2008 17:37:07 + (GMT) [EMAIL PROTECTED] wrote:
> This is what I have in mind:
>
> Have a plperl function that creates connections to all servers in the
> cluster (replication partners), and issues the supplied write query to
> them, possibly
Andrew Sullivan wrote:
On Fri, Jan 18, 2008 at 04:09:45PM +, [EMAIL PROTECTED] wrote:
That's just it - I don't think any user-land libraries would actually be
required. One of supposed big advantages of MySQL is it's straightforward
replication support. It's quite painful to see PostgreSQL
On 18/01/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Dave Page" <[EMAIL PROTECTED]> writes:
> > On 18/01/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
> Ah. That would work better than what I thought you were suggesting, but
> I still don't trust it a whole lot --- there's the problem of "universal
>
Erik Jones <[EMAIL PROTECTED]> writes:
> I recently started up a server created using PITR (exact detail
> below) and received about 125 of these type of errors spanning pages
> in about 10 different tables:
> 2008-01-17 21:47:34 CST 7598 :WARNING: relation "table_name" page
> 5728 is unini
Bricklen Anderson wrote:
Steve Clark wrote:
function from 7.4.x postgres
CREATE FUNCTION update_dns(text, text) RETURNS integer
AS 'UPDATE domain_details SET domain = $2 WHERE domain = $1;
DELETE from domains where domain = $1;
SELECT 1 AS ignore;'
LANGUAGE sql;
I load it into
Greg Smith <[EMAIL PROTECTED]> writes:
> The usual advice, telling them to replicate the binaries used to create it
> in the first place, isn't always the easiest to follow. It seems to me
> that including a "environment at cluster creation" note in $PGDATA like
> Dave suggests would be helpful
Steve Clark wrote:
function from 7.4.x postgres
CREATE FUNCTION update_dns(text, text) RETURNS integer
AS 'UPDATE domain_details SET domain = $2 WHERE domain = $1;
DELETE from domains where domain = $1;
SELECT 1 AS ignore;'
LANGUAGE sql;
I load it into 8.2.5 - then dump it
On Jan 18, 2008, at 2:34 PM, Tom Lane wrote:
Glyn Astill <[EMAIL PROTECTED]> writes:
I'll set up a cron job to remove them for now, however I'll have a
look at pg_standby
Keep in mind that if you delete a log segment that's not yet been sent
to the standby, you've hosed the standby --- you'l
On Fri, Jan 18, 2008 at 04:09:45PM +, [EMAIL PROTECTED] wrote:
>
> That's just it - I don't think any user-land libraries would actually be
> required. One of supposed big advantages of MySQL is it's straightforward
> replication support. It's quite painful to see PostgreSQL suffer purely
>
Glyn Astill <[EMAIL PROTECTED]> writes:
> I'll set up a cron job to remove them for now, however I'll have a
> look at pg_standby
Keep in mind that if you delete a log segment that's not yet been sent
to the standby, you've hosed the standby --- you'll have to take a fresh
base backup and reload t
On 1/18/08, Erik Jones <[EMAIL PROTECTED]> wrote:
> On Jan 18, 2008, at 7:48 AM, Stuart Bishop wrote:
> > plpython !=3D plpythonu.
> >
> > plpython was the 'secure' sandboxed version. The Python devs gave up
> > supporting any sort of sandboxing feature in Python declaring it
> > impossib=
> > le.
Zelinskiy Alexander <[EMAIL PROTECTED]> writes:
> One again it happen.
Looking back at your original post ... maybe you should try a non-Gentoo
kernel. Gentoo doesn't have the greatest reputation for stability, and
on a non-mainstream architecture like sparc64 it'd likely be even buggier
than its
function from 7.4.x postgres
CREATE FUNCTION update_dns(text, text) RETURNS integer
AS 'UPDATE domain_details SET domain = $2 WHERE domain = $1;
DELETE from domains where domain = $1;
SELECT 1 AS ignore;'
LANGUAGE sql;
I load it into 8.2.5 - then dump it out and it is change
On Fri, Jan 18, 2008 at 03:14:41PM +0800, Ow Mun Heng wrote:
> Just wondering if my 'Perceived' feeling that since implementing slony
> for master/slave replication of select tables, my master database
> performance is getting slower.
It imposes a performance penalty, yes.
A
---
[EMAIL PROTECTED] (Ow Mun Heng) writes:
> Just wondering if my 'Perceived' feeling that since implementing slony
> for master/slave replication of select tables, my master database
> performance is getting slower.
>
> I'm constantly seeing a very high amount of IO wait. ~40-80 according to
> vmstat
I recently started up a server created using PITR (exact detail
below) and received about 125 of these type of errors spanning pages
in about 10 different tables:
2008-01-17 21:47:34 CST 7598 :WARNING: relation "table_name" page
5728 is uninitialized --- fixing
Looking in the archives I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Jan 2008 15:08:43 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Joanne Salerno <[EMAIL PROTECTED]> writes:
> > Why is "default_with_oids =false" the default in 8.2.1 ?
>
> Putting OIDs in user tables has been deprecated for quite some time
>
Joanne Salerno <[EMAIL PROTECTED]> writes:
> Why is "default_with_oids =false" the default in 8.2.1 ?
Putting OIDs in user tables has been deprecated for quite some time now.
I suggest looking for a newer version of PgAccess...
regards, tom lane
--
On Fri, 18 Jan 2008, Dave Page wrote:
For just about zero cost we could drop something like:
Architecture: Darwin snake 8.11.1 Darwin Kernel Version 8.11.1: Wed
Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386
Configuration: '--prefix=/usr/local/pgsql83/'
'--enable
I recently went from Postgres 7.4.8 to 8.2.1 (Linux Platform).
After conversion I noticed my forms created with the utility PGACCESS
failed. I found since then that PGACCESS requires oids to perform as I
used it prior to the conversion. If I set "default_with_oids = true"
then the forms work
Thanks Erik,
I'll set up a cron job to remove them for now, however I'll have a
look at pg_standby
--- Erik Jones <[EMAIL PROTECTED]> wrote:
> On Jan 18, 2008, at 11:17 AM, Glyn Astill wrote:
>
> > My server ran out of disk space because my archive directory was
> full
> > ow write ahead logs.
I don't mean to be thick headed, but ...
On Jan 18, 2008 1:11 AM, Blazej Oleszkiewicz <[EMAIL PROTECTED]> wrote:
> Its simple.
... it seems not so simple, as
(1) SVN docs say don't modify the repository before a commit,
(2) I would think that I would need to call pg_dump BEFORE the commit
in o
Hello, Tom.
One again it happen.
postgres 11009 1 0 Jan12 ?00:00:12 /usr/bin/
postmaster -D /data/idx/pgdata --silent-mode=true
postgres 11027 11009 0 Jan12 ?00:26:55 postgres: logger process
postgres 11029 11009 0 Jan12 ?00:00:21 postgres: writer process
po
On Jan 18, 2008, at 11:17 AM, Glyn Astill wrote:
My server ran out of disk space because my archive directory was full
ow write ahead logs.
My warm standby had lost it's mounted NFS volume and thus stopped
reading in the archives from the master.
Would I have run out of space if the standby ha
On Jan 18, 2008, at 11:37 AM, [EMAIL PROTECTED] wrote:
That's one thing. The other problem that most trigger based
replication systems have problems with is propogating schema
changes - because (I think) you can attach triggers to schema
changes.
I presume you mean that you cannot attac
On Friday 18 January 2008 09:17:10 Glyn Astill wrote:
> My server ran out of disk space because my archive directory was full
> ow write ahead logs.
>
> My warm standby had lost it's mounted NFS volume and thus stopped
> reading in the archives from the master.
>
> Would I have run out of space if
On Jan 18, 2008, at 12:00 AM, Albe Laurenz wrote:
0xEDA7A1 (UTF-8) corresponds to UNICODE code point 0xD9E1, which,
when interpreted as a high surrogare and followed by a low surrogate,
would correspond to the UTF-16 encoding of a code point
between 0x88400 and 0x887FF (depending on the value of
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Dave Page wrote:
>> That said, is zlib used by toast or do we have some other code for
>> that? If it is used for that, do we record it's presence or absence in
>> pg_control?
> Nope, toast uses its own compression code.
pg_dump/pg_restore use zlib, bu
Jan de Visser <[EMAIL PROTECTED]> writes:
> So what could make my transaction decide to wait for that other tx?
Usually what this indicates is blocking to acquire a row-level lock,
eg that transaction is waiting to see if it can update a row that the
other one already updated. In 8.1 and later yo
Joshua D. Drake wrote:
That seem that slow for SATA on a write. Assuming 20 (on each
controller) disks random write I would guess the best you could pull off
would be about 200 Megs a second. That's on a good day.
For random writes/reads that sure is OK. I interpreted those numbers as
pure seq
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Actually I think the standard mandates case-folding (though to upper
> case rather than lower, i.e. the other way around)
That's how I read it too. SQL99 5.2 saith
22) The case-normal form of the of a is used for purposes such as and includi
This is what I have in mind:
Have a plperl function that creates connections to all servers in the
cluster (replication partners), and issues the supplied write query to
them, possibly with a tag of some sort to indicated it is a replicated
query (to prevent circular replication).
Have a pos
My server ran out of disk space because my archive directory was full
ow write ahead logs.
My warm standby had lost it's mounted NFS volume and thus stopped
reading in the archives from the master.
Would I have run out of space if the standby hadn't stopped reading
them in?
I.e, should I be dele
Joshua D. Drake wrote:
That seem that slow for SATA on a write. Assuming 20 (on each
controller) disks random write I would guess the best you could pull off
would be about 200 Megs a second. That's on a good day.
For random writes/reads that sure is OK. I interpreted those numbers as
pure seq
2 more things:
Get BBUs for the controllers (If you have not already).
Upgrade to the latest 3ware firmware (code set 9.4.2). There was data
corruption bug with RAID 6.
--
Best regards,
Hannes Dorbath
---(end of broadcast)---
TIP 4: Have you s
"Dave Page" <[EMAIL PROTECTED]> writes:
> On 18/01/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
>> uname is a separate executable. If you do system("uname") you'll get
>> results that reflect how uname was built, not how Postgres was built.
> My suggestion was that we take the output of uname at con
Sean Davis wrote:
We are PURE amateurs, so that is possible. We are running 12-disk RAID6
(750GB drives--this might be a difference from what you are thinking)
partitions under LVM. We have write-cache enabled and are using ext3
filesystems. Any suggestions?
We use the 9650 controllers in RA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Jan 2008 16:54:17 +0100
Hannes Dorbath <[EMAIL PROTECTED]> wrote:
> Sean Davis wrote:
> > 150-200MB/s writing and somewhat faster for reading
>
> That actually seems dead slow. Whatever RAID level you configured,
> there is no sane way for
On 18/01/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
> uname is a separate executable. If you do system("uname") you'll get
> results that reflect how uname was built, not how Postgres was built.
Right, I realise it's a seperate executable, but doesn't configure
rely on it anyway? Meaning if someon
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> What might be better is if we had an explicit endianness mark in pg_control
> rather than relying on users discovering endianness problems by seemingly
> corrupted version numbers.
Chicken-and-egg problem there: you won't know if there's an endianne
"Dave Page" <[EMAIL PROTECTED]> writes:
> On 18/01/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Zero cost and also zero benefit. The missing piece of information here
>> was that the executable being used was running under PPC emulation, and
>> I'll bet money that there would have been nothing in
Dave Page wrote:
> That said, is zlib used by toast or do we have some other code for
> that? If it is used for that, do we record it's presence or absence in
> pg_control?
Nope, toast uses its own compression code.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
Hello,
I have two concurrent transactions, both heavy R/W type things. I now see that
one is backed up behind in the other, and pg_locks shows me this:
sep=# select locktype, transactionid, transaction from pg_locks where not
granted;
locktype| transactionid | transaction
---
[EMAIL PROTECTED] wrote:
On Fri, 18 Jan 2008, Erik Jones wrote:
This is what I have in mind:
Have a plperl function that creates connections to all servers in the
cluster (replication partners), and issues the supplied write query
to them, possibly with a tag of some sort to indicated it i
On 18/01/2008, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Am Freitag, 18. Januar 2008 schrieb Dave Page:
> > It got figured out when someone who knew what they were looking for
> > peeked at the byte ordering in a file which for all we knew at the
> > time might have been damaged anyway
>
> What
Hello,
I have two concurrent transactions, both heavy R/W type things. I now see that
one is backed up behind in the other, and pg_locks shows me this:
sep=# select locktype, transactionid, transaction from pg_locks where not
granted;
locktype| transactionid | transaction
---
Am Freitag, 18. Januar 2008 schrieb Dave Page:
> It got figured out when someone who knew what they were looking for
> peeked at the byte ordering in a file which for all we knew at the
> time might have been damaged anyway
What might be better is if we had an explicit endianness mark in pg_contro
On 18/01/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
> Hm? integer_datetimes is encoded separately and there's a very specific
> error message if it's wrong. The case I think you are remembering was
> caused by a width-of-time_t discrepancy, which should be fixed but it's
> got nothing to do with a
"Dave Page" <[EMAIL PROTECTED]> writes:
> On 18/01/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
>> That's what pg_control is for. We figured out easily enough that this
>> was an endianness problem; having had "big endian" somewhere in
>> cleartext wouldn't have improved matters.
> It got figured ou
On Fri, 18 Jan 2008, Erik Jones wrote:
Is there any reason why PostgreSQL replication solutions are all add-on 3rd
party ones?
Because no one solution would be appropriate for everyone. The core team and
contributors feel that their time is better spent on the database itself
rather than
On 18/01/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Dave Page" <[EMAIL PROTECTED]> writes:
> > Note to the other hackers - is it worth having initdb dump the
> > architecture details and configure options used into the cluster in a
> > human readble form so we can pickup on this sort of thing mor
Sean Davis wrote:
150-200MB/s writing and somewhat faster for reading
That actually seems dead slow. Whatever RAID level you configured, there
is no sane way for it to be that slow. Is this a RAID 5/6 array? Did you
forgot to align your file system to stripe boundaries?
--
Best regards,
Ha
Sean Davis wrote:
I know this is off-topic, but I know lots of folks here deal with very large
disk arrays; it is hard to get real-world input on machines such as these.
In my experience the 3ware support staff is competent and replies
within one business day. Just sign up at:
https://www.3w
On Jan 18, 2008, at 9:21 AM, [EMAIL PROTECTED] wrote:
Hi,
Is there any reason why PostgreSQL replication solutions are all
add-on 3rd party ones?
Because no one solution would be appropriate for everyone. The core
team and contributors feel that their time is better spent on the
datab
On Jan 18, 2008, at 7:48 AM, Stuart Bishop wrote:
plpython !=3D plpythonu.
plpython was the 'secure' sandboxed version. The Python devs gave up
supporting any sort of sandboxing feature in Python declaring it
impossib=
le.
Someone should definitely take a look at this: http://
sayspy.blo
"Dave Page" <[EMAIL PROTECTED]> writes:
> Note to the other hackers - is it worth having initdb dump the
> architecture details and configure options used into the cluster in a
> human readble form so we can pickup on this sort of thing more easily
> in the future?
That's what pg_control is for.
"Dave Page" <[EMAIL PROTECTED]> writes:
> As for the real problem (on the same hardware), when you rebuilt
> Postgres on your new machine did you change any of the configure
> options that MacPorts would have used from what would have been used
> previously (I assume they can be overridden)?
There
Hi,
Is there any reason why PostgreSQL replication solutions are all add-on
3rd party ones? Is there any reason why replication couldn't be
implemented using triggers and a handful of stored procedures? This is
what I have in mind:
Have a plperl function that creates connections to all serve
On 18/01/2008, Stefan Schwarzer <[EMAIL PROTECTED]> wrote:
> I don't understand it either, which is why I was wondering if it was
> running under some PPC emulation (can you run standard mac software or
> do you have to get special Intel versions).]
Yes, Apple have an emulation layer called Rosett
Ok, it seems to be related to a Intel/PPC issue, as Martijn and Tom
suggested.
So, I copied all files to a PPC, but which runs Linux - don't know if
this is important. Now, it tells me:
"Fatal error: Incorrect checksum on control file"
Any way out of this? Thanks for any advice.
That's the ki
Alexandre da Silva wrote:
> Hello,
> someone can tell me if is secure to create external python modules and
> import them to functions/procedures/triggers to use?
Its fine as long as you trust the users with write access to your PYTHONP=
ATH.
> Another question is that I have read in some discuss
On 18/01/2008, Stefan Schwarzer <[EMAIL PROTECTED]> wrote:
> Ok, it seems to be related to a Intel/PPC issue, as Martijn and Tom
> suggested.
>
> So, I copied all files to a PPC, but which runs Linux - don't know if
> this is important. Now, it tells me:
>
> "Fatal error: Incorrect checksum on cont
On Jan 18, 2008 7:25 AM, Stefan Schwarzer <[EMAIL PROTECTED]> wrote:
> >
> >>> Did you just move from a PPC-based Mac to an Intel-based one?
> >>> If so, you're out of luck --- you need to go back to the PPC
> >>> to make a dump of those files.
> >>>
> >>
> >> No, I just re-installed my Intel M
Did you just move from a PPC-based Mac to an Intel-based one?
If so, you're out of luck --- you need to go back to the PPC
to make a dump of those files.
No, I just re-installed my Intel Mac. First I just upgraded from
Tiger to Leopard (without getting my database to run; but I didn't
put
On Jan 18, 2008 7:45 AM, Gregory Williamson <
[EMAIL PROTECTED]> wrote:
> Mayuresh Nirhali wrote:
> >
> > Josh Harrison wrote:
> > >
> > >
> > > Thanks .
> > > We have around 3TB of data now running in Oracle. I have done
> > > replication in postgresql but not much in Oracle. Is there a way you
Mayuresh Nirhali wrote:
>
> Josh Harrison wrote:
> >
> >
> > Thanks .
> > We have around 3TB of data now running in Oracle. I have done
> > replication in postgresql but not much in Oracle. Is there a way you
> > can replicate between Oracle and Postgresql. For writing the custom
> > codes do
Nico Sabbi wrote:
> yet I find disturbing that Postgres doesn't make the effort
> to respect the case specified by the user.
It does -- if you quote the names.
> If I created a field
> called "REF" why should Postgres call it "ref" in the output of queries
> if the standard doesn't specify any o
On Jan 18, 2008, at 1:14 PM, Nico Sabbi wrote:
Tom Lane ha scritto:
The SQL standard specifies that unquoted identifiers are case-
insensitive.
You're welcome to spell them as camelCase in your source code if you
feel like it, but don't expect that
Nico Sabbi wrote:
>
> Tom Lane ha scritto:
> > Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> >
> >> After discovering that pg_get_serial_sequence behaves in a bit
> >> strange way[1] when it deals to case sensitiveness
> >>
> >
> > The SQL standard specifies that unquoted identifier
Erik Jones wrote:
On Jan 17, 2008, at 1:08 PM, Greg Smith wrote:
On Thu, 17 Jan 2008, Tom Lane wrote:
There isn't any good way to guarantee time coherence of dumps
across two databases.
Whether there's a good way depends on what you're already doing.
If you're going to the trouble of
On Fri, 18 Jan 2008 13:14:33 +0100
Nico Sabbi <[EMAIL PROTECTED]> wrote:
> yet I find disturbing that Postgres doesn't make the effort
> to respect the case specified by the user. If I created a field
> called "REF" why should Postgres call it "ref" in the output of
> queries if the standard doesn
Tom Lane ha scritto:
Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
After discovering that pg_get_serial_sequence behaves in a bit
strange way[1] when it deals to case sensitiveness
The SQL standard specifies that unquoted identifiers are case-insensitive.
You're welcome to spell th
Josh Harrison wrote:
Thanks .
We have around 3TB of data now running in Oracle. I have done
replication in postgresql but not much in Oracle. Is there a way you
can replicate between Oracle and Postgresql. For writing the custom
codes do you suggest any preferred language ...like java, perl
Tom Lane wrote:
>> But I'm still getting this error when loading the data into the new
>> database:
>
>> ERROR: invalid byte sequence for encoding "UTF8": 0xeda7a1
>
> The reason PG doesn't like this sequence is that it corresponds to
> a Unicode "surrogate pair" code point, which is not suppo
88 matches
Mail list logo
